Alphalyr helps you boosting your omnichannel commerce with the data that matters.
Using this destination you can connect your activities and events with Alphalyr Marketing Studio.
The Alphalyr Marketing Studio destination provides the following key features:
- Events structure: our Events reference supports Alphalyr's page types, 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 Rakuten Advertising.
Settings | Description |
---|---|
Client Public Key | Required Your unique public key as given by Alphalyr Marketing Studio. This setting supports dynamic values [1]. |
Customer Type | Defines your customer type. Takes the value 0 when it is an old client and 1 when it is a new one. This setting supports dynamic values [1]. |
User Unique Identifier (UUID) | UUID value of the user's cookie. Following the latest updates to the ITP protocol on Safari / iOS, Alphalyr strongly recommends that you use a "server" cookie coming directly from your first party domain. This setting supports dynamic values [1]. |
Custom Data | Additional data that can be added for custom data processing. This setting supports dynamic values [1]. |
Is SPA | Whether your website is a Single Page Application. |
GDPR Consent | GDPR consent. It takes the value 1 when GDPR applies or 0 otherwise. This setting supports dynamic values [1]. |
Consent Status for Ads & Marketing | Consent status for ads & marketing. It takes the value 1 if the user has consented to the use of his data for targeting and marketing or 0 otherwise. This parameter is transmitted to Alphalyr's partners. This setting supports dynamic values [1]. |
Consent Status for Performance | Consent status for performance. It takes the value 1 if the user has consented to the use of his data for the measurement of performance measurement or 0 otherwise. This parameter is transmitted to Alphalyr's partners. This setting supports dynamic values [1]. |
{% hint style="info" %}
[1] This feature allows you to set an event property holding a dynamic value by adding two open braces ({{
) in front of your property name and two close braces (}}
) at the end (E.g. {{myEventPropertyPathAndName}}
).
{% endhint %}
{% hint style="info" %} Use Destination filters to specify your matching events. {% endhint %}
Commanders Act Events | Alphalyr Page Types |
---|---|
purchase |
purchase |
view_cart |
cart |
view_item |
product |
view_item_list |
category |
[Any Other Event] |
home |
{% hint style="info" %} Most properties can be remapped using our "Smart Mapping" feature. {% endhint %}
Commanders Act Properties | Alphalyr Properties |
---|---|
(event_name) | page [1] |
Client Public Key | aid |
user.email_md5 | cid |
| uuid [2] |
context.page.referrer | referrer |
context.device.ip | ip_address [3] |
context.device.user_agent | user_agent |
(eventModel.app.name) | deviceType [4] |
context.page.url | path [5] |
items.X.id | prodId [6] |
items.X.product.name | prodDescription [6] |
items.X.product.price | prodPrice [6] |
item_list_id | catId [7] |
item_list_name | catDescription [7] |
items.X.id :items.X.quantity :items.X.product.price | products [8][9] |
currency | currency [9] |
| totalPrice [9][10] |
value | totalPriceWithTax [11] |
shipping_amount | shippingPrice [11] |
id | reference [11] |
Customer Type | new [11] |
coupon | discountCode [11] |
items.X.discount | discountAmount [8][11] |
Custom Data | customData [11] |
GDPR Consent | gdpr_consent |
Consent Status for Ads & Marketing | consent_ads |
Consent Status for Performance | consent_performance |
context.device.lifecycle.session_id | gaSessionId [12] |
{% hint style="info" %}
[1] See Quick reference for more details.
[2] Field automatically hashed with SHA256 if passed in clear. Priority order is provided on the left column.
[3] Field anonymized.
[4] This is either m
or d
depending if eventModel.app.name
is set or not.
[5] The pathname
part of context.page.url
is set: additional parameter are added to the request based on searchParams
(See URL object for more details).
[6] For Alphalyr product
page type only.
[7] For Alphalyr category
page type only.
[8] All items are taken into account.
[9] For Alphalyr purchase
and cart
page type only.
[10] Depending if Alphalyr page type is purchase
or cart
then revenue
or value
is used respectively.
[11] For Alphalyr purchase
page type only.
[12] When Is SPA
is flagged only.
{% endhint %}