Exactag

This destination is currently under final review and will be available soon.

Exactag is a marketing performance platform specializing in multi-touch attribution and marketing mix modeling. Using this destination you can enable server-side tracking to send events to Exactag.

Key features

The Exactag destination provides the following key features:

• Events structure: our Events reference model covers Exactag's events, meaning that your data is properly bridged to the expected fields in an optimized way.

• Prebuilt mappings: data mapping for event-based destinations happens automatically, which simplifies user inputs.

• Smart mapping: data mapping can be readjusted using your datalayer defined fields.

• Event mapping: change standard mapping between Exactag events and yours.

Destination setup

Configuration

Settings	Description
Campaign Code	Required Encrypted campaign code.
Event Mapping	Change the standard mapping between Exactag events and your events or add new mappings.
Custom Event Properties	Send custom properties related to events.

Quick reference

Commanders Act Events	Exactag Events (sitegroup)
[Any Event]	[Any Event] [1]

1. Your same event name is sent to Exactag as sitegroup . See Event Mapping in Configuration to change the standard mapping based on your needs.

Field mappings

Properties can be remapped using our Smart Mapping feature.

For optin users (See property optout), at least one of the following user identifier properties is required:

• Partner User Identifier (euk) • Exactag User Key (uk) • Device Mobile Identifier (did)

If you need to use Exactag's "Anonymous Attribution", the property Group Key (gk) is required.

Smart Mapping Fields	Commanders Act Default Properties	Exactag Properties
-	Campaign Code	campaign [*]
-	Event Mapping event_name	sitegroup [*][1]
Page URL	context.page.url	host [*][11] site [*][11] search [11] protocol [11]
Page Referrer	context.page.referrer	referrer [*][12]
Session Number	context.device.lifecycle.session_number	sescount [*][2]
Event Number	context.event_id	sesevent [*][3]
Partner User Identifier	user.consistent_anonymous_id	euk [4]
Exactag User Key	partners.exactag.user_key	uk [4][5]
Device Mobile Identifier	context.device.advertising_id	did [4]
Group Key	partners.exactag.group_key	gk [6]
Optout	partners.exactag.optout	optout [7]
Optin	partners.exactag.optin	optin [8]
Transaction Id	id	orderid [9]
Commission Level	partners.exactag.level	level
User Identifier	user.id	customerid [10]
Transaction Value	value	totalprice
Device IP	context.device.ip	ipaddress [13]
Device User Agent	context.device.user_agent	useragent [14]
Session Identifier	context.device.lifecycle.session_id	sessionid [15]
Consent	partners.exactag.consent	consent [16]
IAB GDPR Consent	partners.exactag.consent_string	consent_string [17]
Browser	partners.exactag.browser	browser [18]
Operating System	partners.exactag.os	os [18]
Operating System Version	partners.exactag.os_ver	os_ver [18]
Language	partners.exactag.lang	lang [18]
Device Type	partners.exactag.device_type	device_type [18]
Device Name	partners.exactag.device_name	device_name [18]

* Mandatory property. 1. See Event Mapping in Configuration to change the standard mapping based on your needs. 2. Session number from 1 to x (1 : new visitor, >1 : recurring visitor). 3. Event number from 1 to x (1 : first page impression in this session). 4. See Fields mappings for more details on how Exactag identifies users. 5. Exactags unique identifier for the person or device. This value must be a valid md5 hash. 6. A unique identifier for an anonymous group of multiple users. This value must be a valid md5 hash combined with the group expire timestamp (urlencoded or base64url encoded value). Mandatory for "Anonymous Attribution". 7. If set to 0 or missing, the request will be treated as the user has opted in. Set with 1 if the user has opted out. 8. If the campaign requires an optin, as internal configuration, then optin=0 or no parameter passed will be treated as an optout. optin=1 is required for normal processing. If the campaign has no setting, then optin can be ignored and optin=1 will be assumed. 9. Used for deduplication. 10. Used for cross device. 11. Value retrieved from Page URL . 12. Can be anonymized by sending only the referral domain. 13. Required for geo location information. Optional, for for opted out users, if geo location information is not neede. 14. Optional if device information is not desired. It can be anonymized by sending only extracted values. See "Smart Mapping" fields: Browser , Operating System , Operating System Version , Language , Device Type and Device Name . 15. Optional for opted out users. 16. JSON object for type or partner based consent. 17. IAB GDPR consent string. 18. This can be used to send anonymized extracted values instead of setting a value in Device User Agent .