See also:
- Tracking parameters in Ometria
- Custom tracking parameters
- Default tracking parameters for email
- Default tracking parameters for SMS
Parameter | Data |
utm_medium |
If you have
Note: If you're using email, SMS and push in the same campaign,
utm_medium is assigned based on the node by default. This means that the campaign name will be the same regardless of the channel, but the medium will be different. However, if you change the parameter at campaign level then this overrides the default, so all channels are assigned the same utm_medium . |
utm_source |
transactional |
utm_campaign |
campaign_title |
om_campaign |
om_[campaign_hash]_version id]_[node_id] |
utm_content
utm_content
isn't a default field, but if set it picks up the name of the action node.
If you want to track a specific node from an automation campaign, you can set {{message.node_title}}
which pulls through the title of the node (e.g. send SMS, send email, send push notification, etc.)
This is particularly useful in a cross-channel campaign which includes both email and push.
Make sure you've named your action nodes something easily recognisable.
Tracking parameter hierarchy
This section explains the order in which tracking parameters are overridden.
An override means that:
- if a parameter doesn't exist on the previous level, it gets added
- if a parameter does exist on the previous level, the old value is discarded and the new value is used for it
Push notifications
- Parameters defined on URLs in the push template.
Overridden by:
Overridden by:
- Account level parameters for email
Overridden by:
- Campaign level parameters set for email
Comments
0 comments
Article is closed for comments.