Alphalyr Marketing Studio
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.
Key features
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.
Automatic hashing: information is automatically hashed matching partner specifications.
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.
Destination setup
Configuration
Settings | Description |
---|---|
|
|
| Defines your customer type. Takes the value |
| 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]. |
| Additional data that can be added for custom data processing. This setting supports dynamic values [1]. |
| Whether your website is a Single Page Application. |
| GDPR consent. It takes the value |
| Consent status for ads & marketing. It takes the value |
| Consent status for performance. It takes the value |
[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}}
).
Quick reference
Use Destination filters to specify your matching events.
Commanders Act Events | Alphalyr Page Types |
---|---|
|
|
|
|
|
|
|
|
|
|
Field Mappings
Most properties can be remapped using our "Smart Mapping" feature.
Commanders Act Properties | Alphalyr Properties |
---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
[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.
Last updated