Offline Conversions

Owned by Audrey Marissal
Last updated: Dec 19, 2024
3 min read

It is possible to import offline conversion into Adloop (call-center, shop sales…) and to integrate them in the path-to-conversions, offering you online/offline reconciliation.

To integrate offline conversions into Adloop, we use a CAX destination. Data must then first be sent to CAX following this process.

Β 

Technical requirements

To integrate offline conversions into the paths-to-conversion, we must have a reconciliation key. Usually, those are hashed emails, hashed phone numbers…

This reconciliation ID must be present in one of the Analytics dimension (on GA4 or Piano) and must be in the file sent to CAX, otherwise we won’t be able to match the data.

Please check in the Console / Network, that the dimension with the reconciliation key (ex: phone_number) is present at the same time than the Adloop Code in the Adloop dimension.

Check our documentation page about checking the presence of the Adloop Code.

If this step is not working, the reconciliation can’t work!

CAX file requirement :

  • Reconciliation key

  • Order ID

  • A column offline conversions

  • Dimensions : source (if your file contains several sources of offline conversions, ex: Call-Center, Shop), any other details, any other details useful for analysis (ex: City, Brand…)

  • Metrics : Order, Order Value, any other details useful for analysis (ex: Visits, Calls)

Adloop destination set-up

You’ll be setting up the Adloop destination inside the CAX platform with the help of your consultant.

Here are some general informations about what needs to be set-up:

When adding the Adloop destination in CAX, several informations must be filled out:

  • Dataset URL : the Adloop URL of the account (without anything after the .co)

image-20241218-144808.png

  • Dataset ID : can be found in the URL (number after the .co) or on the site page accessible from the left-hand Adloop menu (first column)

image-20241218-144827.png

  • Name : name of your source in Adloop, so give it a nice and readable name (ex: Call-Center and not call_center_data_client.csv)

  • Mapping :

    • Before doing your mapping, you’ll need a payload

    • You have to map out all the dimensions & metrics you want to import

      • "status":{ name in the payload

        Β Β Β Β Β Β Β  "slug":"status", technical name in Adloop, please use small letters & - (not _)

        Β Β Β Β Β Β Β  "name":"Status of the Call" name that will be visible in Adloop in the reports etc.

      • Additional line for metrics:

        • "is_conversion":true to indicate that a metric is a conversion (ex: purchase)

        • "is_conversion_value":true to indicate that a metric is a conversion value (ex: purchase revenue)

    • It is necessary to have in the payload type_value : "offline". This information doesn’t need to be in the file, it can be added manually in the payload as a fixed value.

  • Analytics custom dimension : Indicate the name of the dimension in which the reconciliation key can be found in the Analytics source

    • For GA4: name of the dimension (ex: telephone_hashed)

    • For Piano Analytics: name of the dimension (ex: telephone_hashed)

    • It is possible to add several dimensions (ex: reconciliation both on telephone or email) just separate them by a comma (,) (ex: telephone_hashed,email_hashed)

  • Authentification token: Your consultant will have this information

Β