Run activation templates - standard audience overlap activation or custom sql_activation templates.
Execute activation templates that export matched segments to collaborators.
sql_activation (custom activation template)Note:
{DB}must be replaced with the actual DCR database discovered in the parent skill.
After user selects a template in the parent skill:
If template name matches standard_audience_overlap_activation_v*:
→ Follow Standard Activation Workflow below
Else (custom sql_activation template):
→ Follow Custom Activation Workflow below
For standard_audience_overlap_activation_v* templates with known, fixed parameters.
Use data offerings from router Step 1-5. The current account's table should always be the activation source (where segments are exported from).
ORGNAME.ACC_NAME)collaborator_identifier_aliases, find the collaborator name that maps to the current accountSHARED_BY column in data offerings| SHARED_WITH Value | SHARED_BY | Table Placement | Alias | Role |
|---|---|---|---|---|
Exactly "LOCAL" | Current account | local_view_mappings.my_tables[0] | c1. | YOUR data (activation source) |
Not "LOCAL" | Current account | view_mappings.source_tables[1] | p2. | YOUR data (activation source) |
Not "LOCAL" | Partner | view_mappings.source_tables[0] | p1. | PARTNER data (source) |
Key Points:
c1. or p2.)p1."LOCAL" indicates a local tableValid Configurations:
Config A: Local + External
When current account's table has SHARED_WITH = "LOCAL":
view_mappings:
source_tables:
- "PARTNER.offering_id.table" # p1. (SHARED_BY = partner)
local_view_mappings:
my_tables:
- "LOCAL.offering_id.table" # c1. (SHARED_WITH = "LOCAL", current account)