Campaign Analysis Legacy
Only for Campaign Analysis Module (ex Mix Commander) customers
Last updated
Only for Campaign Analysis Module (ex Mix Commander) customers
Last updated
This destination allows you to collect events and map it for the module Campaign Analysis It can also turns events from Normalized Datalayer into touchpoints for Campaign Analysis module.
With this destination, you can use 4 standard events. To receive events in this destination, it requires as event name the 'Standard event name' described in the following array. Here's the list of Campaign Analytics touch points names vs Standard events names:
| Campaign Analysis touch point | Standard event name |
|---|---|
impressions | ad_view |
clicks | ad_click |
sites | page_view |
orders | purchase |
If you need more information about these events, check the section Events reference
This destination will do an automatic mapping between the Campaign dimensions and the Standard properties. Here's the list of the automatic configuration done by this destination:
| Campaign properties | Standard dimensions | Campaign Dimension labels |
|---|---|---|
amount | value | Amount |
cmp | campaign | Campaign |
chn | medium | Channel from medium |
cty | user.country | Country |
currency | currency | Currency |
dev | context.device.terminal_type | Device |
e | user.email | |
fmt | ad_format | Format |
kw | keyword | Keyword, will be singular in NDL |
med | medium | Medium |
n_customer | user.is_new_customer | New Customer |
orderid | id | Order id |
os | status | Order Status |
ot | type | Order Type |
p | page_name | Page Name |
pt | page_type | Page Type |
ref | context.page.referrer | Referrer |
src | source | Source |
tclid | ad_cost_id | tclid |
user_id | user.id | User id |
If you use custom properties, or if you want to modify one or some of theses campaign dimensions with another property then the ones listed above, you will have to use the mapping table.
In all cases, a hand mapping is possible (between dimensions and properties). It will take the priority and override native mapping. Use the mapping table menu to make your own correspondence table:
If you add a new custom dimension in your Campaign Analytics, you must to declare it manually also in this table of the destination's settings
If you do not want to use automatic mapping of dimensions with event properties, you can check the option "disable automatic configuration"
This action will block all automatic mapping between Campaign dimensions and Standard properties
Before to send your events to this destination you can, if needed, transform them to rename or remove some properties. Enter on the left the property name you want to add, delete or modify. Then enter on the right the property name where the value stands (or leave empty to remove the property)
You have to specify which event is concerned by this destination. Here's an example for a purchase (orders)
Don't forget to setup a consent filter to be RGPD compliant as well
ts_override property can be used to change the timestamp of an event
Example:
https://collect.commander1.com/events?tc_s={site_id}}&token={token}&medium=seo&source=google&ts_override=1716888588&event_name=ad_click&campaign=sales_2024
