Skip to end of banner
Go to start of banner

Advanced Data Integration Use Cases

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Current »

In this post we are listing additional Data Integration use cases which can be done in the Boxlaino Data Platform:

Criteo Audience

Our Winning Interaction platform can create various types of Audiences, both for Google Ads, but also for other platforms. One of these platforms is Criteo https://help.criteo.com/kb/guide/en/about-audiences-0EJNOqUqYu/Steps/842036

The audience feed is based on dynamic Contact Lists About Contact List Segments | Help Criteo and is using the Criteo API:https://developers.criteo.com/marketing-solutions/docs/audiences

The following Audiences can be created:

  • All customers

  • All newsletter subscribers

  • New customers

  • Customers who bought in the last year but not in the last month

  • Customers with high Customer Lifetime Value

Follow the onboarding list from Criteo https://developers.criteo.com/marketing-solutions/docs/onboarding-checklist

For integration purposes, Boxalino requires the application credentials (application_id, client_id, client_secret, allowed_grant_type (must be client_credentials )

Allow the application to Manage Audiences in the Authorization section & Activate app.

Facebook Newsletter Subscriptions

This is a case of immediate chaining of data integrations based on https://developers.facebook.com/docs/marketing-api/guides/lead-ads/ .

As soon as a subscriber registers, a Webhook should be triggered as Custom integration:

  • Custom integration - Using Webhooks and Facebook Graph API. A Webhook is an HTTP callback that occurs when something happens, which in turn invokes a simple event notification via the HTTP POST call. See Lead Ads Webhooks for more information.

Which directly saves the data in Google BigQuery.

Then the system would immediately push the data to a Push DataFeed which has to be integrated by the newsletter system.

Data Feed (import) → API Requests → Data Feed (export)

In this case, we want to be able to chain 3 processes:

  1. Data are pushed to our Data Integration platform with a Load Feed Request: https://boxalino.atlassian.net/wiki/spaces/BPKB/pages/842629121/Data+Feeds+DF#LOAD-FEED-REQUEST

  2. A BigQuery view is then called in a loop providing Narrative API requests which are executed and for which the results are integrated in BigQuery, which will probably require a small extension of our https://boxalino.atlassian.net/wiki/spaces/BPKB/pages/842629121/Data+Feeds+DF#LOAD-FEED-REQUEST

  3. A Read (https://boxalino.atlassian.net/wiki/spaces/BPKB/pages/842629121/Data+Feeds+DF#READ-FEED-REQUEST ) or View (https://boxalino.atlassian.net/wiki/spaces/BPKB/pages/842629121/Data+Feeds+DF#VIEW-FEED-REQUEST ) or Json (https://boxalino.atlassian.net/wiki/spaces/BPKB/pages/842629121/Data+Feeds+DF#JSON-FEED-REQUEST ) feed is the pushed to the requesting 3rd party

  • No labels