Button

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

Button provides deep linking and optimizing affiliate, creator & social traffic. Using this destination you can leverage Button Orders API to report a purchase.

Key features

The Button destination provides the following key features:

• Events structure: our Events reference covers Button Orders API, 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.

• Support for multi-item data: information included in the item array is bridged to Button.

Destination setup

Configuration

Settings	Description
API Key	Required Your Button generated API key. For more details, you can check the following LINK.
Source Token	Button source/attribution token. This field is optional to create an order, but is required for attribution. When testing your integration, you should send dummy source tokens to Button, in the following format: ^fakesrctok-[a-f0-9]{16}$ (E.g. fakesrctok-abcdef0123456789). URL safe string up to 255 characters.
Custom Event Properties	Map your custom event properties by setting their field names in Button property name and adding the field name holding the value in Your event property. In the column Your event property position you should keep the default value Default (root) as it better fits most scenarios. In case you select either In "items" {items.X} or In "product" {items.X.product} this destination will look for the input event property starting from the items or product level respectively and set the value in line_items.X.attributes .

Quick reference

Commanders Act Events	Button Tracking
[Any event]	Order record

Field mappings

Properties can be remapped using our Smart Mapping feature.

Smart Mapping Fields	Commanders Act Default Properties	Butto Properties
Transaction Id	id	order_id [*]
Transaction Revenue	revenue	total [*]
Currency	currency	currency [*]
Item Id	items.X.id	line_items.X.identifier [*]
Item SKU	items.X.id	line_items.X.sku [*]
Item Price Item Quantity Item Discount	items.X.product.price [*] items.X.quantity [*] items.X.discount	line_items.X.total [*][1]
Item Category 1 Item Category 2 Item Category 3 Item Category 4 Item Category 5	items.X.product.category_1 [*] items.X.product.category_2 items.X.product.category_3 items.X.product.category_4 items.X.product.category_5	line_items.X.category [*][2]
Item Description	items.X.product.name	line_items.X.description [*]
-	Source Token	btn_ref
Purchase Date Event Timestamp	partners.button.purchase_date context.event_timestamp	purchase_date [3]
Total As Decimal	partners.button.total_as_decimal	total_as_decimal [4]
User Id	user.id	customer.id
User Email	user.email	customer.email_sha256 [5]
Device Mobile Identifier	context.device.advertising_id	customer.device_id
Is User New	user.new_user	customer.is_new_user
Customer Transaction Id	id_variant	customer_order_id
Partner Order Channel	partners.button.order_channel	partner_order_channel [6]
Finalization Date	partners.button.finalization_date	finalization_date
Item Quantity	items.X.quantity	line_items.X.quantity
Item UPC	items.X.id	line_items.X.upc
Item Coupon	items.X.coupon	line_items.X.attributes.coupon_code

* Mandatory property. 1. Based on the values on the left and depending on the property partners.button.total_as_decimal . 2. Set as an array with all the provided categories. 3. if partners.button.purchase_date is not provided, context.event_timestamp is used. 4. Pass true (Boolean) if you want to set decimal values for both Button property total and line_items.X.total , false (Boolean) or don't set otherwise. 5. If it's passed in clear text, it's automatically hashed via SHA256. 6. Accepted values: app and webview. If it's not provided, automatically set to app when property context.app.name is non-empty. Default value: webview.