Platform X
Search…
⌃K

Piano Analytics (AT Internet)

Piano Analytics is the successor of AT Internet Analytics Suite 2 (AS2). It's a user-centric tool that simplifies product & marketing analytics, while ensuring data quality. Your data will be sent server-side getting the most from AT Internet Collection API and in form of events.
The Collection API is only available for Piano Analytics. If your perimeters are certified (ACPM/Mediamétrie), you can't use Piano Analytics and this destination. You can check the following compatibility table to get more insights on supported features by product.

Key features

The AT Internet destination provides the following key features:
  • Events structure: our Events reference matches AT Internet's one, 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.
  • Custom events: you can freely push custom events based on your specific needs.
  • Support for multi-item data: information included in the item array is dispatched to AT Internet.
  • User identifier: you can openly select a user identifier field for logged users.

Destination setup

Before you get started with this destination, ensure you have access to Piano Analytics.
The client-side unique visitor identifier is recommended and is retrieved by getting the value of thepa_vid,atuserid, orxtidccookie in this priority order.

Configuration

Settings
Description
Side Id
Required
The identifier of the site the data belongs to (E.g. 628087). This can be found in the AT Internet interface following
SETTINGSData Collection PortalToolsSite Management and selecting your site.
Secured Collection Domain
Required
The SSL Domain on which information is collected (E.g. logs1412.xiti.com). This can be found in AT Internet interface following
SETTINGS Data Collection PortalToolsSite Management and selecting your site.
Custom Event Properties
Map your custom event properties by setting their field names in Event property name and adding the field name holding the value in Commanders Act event property or static value. E.g. if you inputsizein the Event property name and properties.items.0.product.size in Commanders Act event property or static value, you'll have a custom event property in Piano Analytics calledsizewith a value based on the content of the field properties.items.0.product.size [1]. You also have the option to set a static string/numeric value in Commanders Act event property or static value. To ensure that custom event properties are picked up by Piano Analytics, you need to create them first by following
SETTINGSData ManagementData ModelProperties.
Custom User Properties
Map your custom user properties by setting their field names in User property name and adding the field name holding the value in Commanders Act event property or static value. E.g. if you inputcustomer_zipcodein User property name andproperties.user.zipcode [1] in Commanders Act event property or static value, you will have a custom user property in GA4 calledcustomer_zipcodewith a value based on the content of the fieldproperties.user.zipcode. You also have the option to set a static string/numeric value in Commanders Act event property or static value.
To ensure that custom user properties are picked up by Piano Analytics, you need to create them first by following
SETTINGSData ManagementData ModelProperties.
User Identifier
You can bridge your selected user identifier for logged users. More details are available following this LINK.
Custom Property
When selecting "[Custom Property]" as value for the above "User Identifier", this field will show up so you can specify a custom field holding the value for the user identifier [1].
[1] Using "dots" (".") you can navigate deeper to the specific field you want to get the value of. See Events reference for more details on the standard field names by event. You can also freely set custom fields: there are no boundaries.

Quick reference

Commanders Act Events
AT Internet Events
add_payment_info
cart.payment
add_shipping_info
cart.delivery
add_to_cart
product.add_to_cart
add_to_wishlist
product.add_to_wishlist [*]
begin_checkout
cart.begin_checkout [*]
generate_lead
generate_lead [*]
login
user.login [*]
page_view
page.display or product.page_display [1]
purchase
transaction.confirmation and product.purchased [2]
refund
refund [*]
remove_from_cart
product.remove_from_cart
search
internal_search_result.display
select_content
select_content [*]
select_item
select_item [*]
sign_up
user.sign_up [*]
view_cart
cart.display
view_item
product.display
view_item_list
page.view_item_list [*]
[Custom Event]
[Custom Event] [*]
[*] Custom events must be added to the AT Internet Data Model first or they won't be processed. You can add new events by following
SETTINGSData ManagementData ModelEvents. [1] Ifproperties.page_typeis equal toproductthenproduct.page_displayis sent, otherwise,page.display. [2] Aproduct.purchasedwill be sent for each product being purchased.

Field Mappings

Commanders Act Properties
AT Internet Properties
properties.page_name
page
properties.value
generate_lead_value
cart_turnovertaxincluded
properties.currency
generate_lead_currency
cart_currency
properties.id
transaction_id
generate_lead_id
properties.item_list_name
view_item_list_name
properties.method
login_method
sign_up_method
properties.search_term
ise_keyword
properties.items.X.id
product_id
properties.items.X.product.name
product
properties.items.X.variant
product_variant
properties.items.X.product.brand
product_brand
(properties.items.X.discount > 0)
product_discount [1]
properties.items.X.product.price
product_pricetaxincluded
properties.items.X.product.currency
product_currency
properties.items.X.product.category_1
product_category1
properties.items.X.product.category_2
product_category2
properties.items.X.product.category_3
product_category3
properties.items.X.product.category_4
product_category4
properties.items.X.quantity
product_quantity
cart_quantity [2]
properties.items.X.coupon
product_promocode
properties.coupon
transaction_promocode
properties.payment_method
payment_mode
properties.shipping_amount
shipping_costtaxincluded
properties.shipping_tier
shipping_delivery
properties.cart_id
cart_id
properties.revenue
cart_turnovertaxfree
properties.items.length
cart_nbdistinctproduct
properties.user.id
properties.user.email
properties.user.email_md5
properties.user.email_sha256
[custom_property]
user_id [3]
device.manufacturer
device_manufacturer
device.model
device_model
device.screen.height
device_screen_height
device.screen.width
device_screen_width
[1] Boolean value:trueorfalse. [2] Sum allproperties.items.X.quantity. [3] Depending on the drop-down selection (SeeUser Identifierin theConfigurationsection), a specific Commanders Act property is used.

Headers parameters

Commanders Act Properties
AT Internet Fields
device.user_agent
User-Agent
page.location
Referer
device.ip
X-Forwarded-For
Last modified 1mo ago