Introduction

Angler AI's predictive CAPI integration for WooCommerce stores consists of two key steps:

• Install Angler’s Tag: Set up the Angler tag using either Google Tag Manager or by directly embedding it in JavaScript. This guide assumes implementation will be carried out through Google Tag Manager.
• Historical Data Extraction: Perform a one-time extraction of historical transaction data, including orders, customers, and products, ideally covering the past two years. For businesses that process offline orders (e.g., system generated subscription refill orders, in-store purchases or telesales), Angler will need regular updates to the historical transaction data. These updates should ideally occur in near real time or at least be refreshed daily.

Install Angler's Tag

Please contact your Angler's onboarding specialist for your dedicated Angler AI tag. They will provide you the details of your Angler workspace ID and API key will be provided along with the actual tag.

Please map your existing e-commerce funnel events to Anger’s standard events as much as possible. This document should provide you all the information you need.

If you are unable to map it to a standard event, please send those events as custom event with custom_event_name.

Historical Data Extraction

Angler AI can receive historical data and ongoing backend data, if necessary, in two ways:

• Flat file transfer through AWS S3, a cloud storage service;
• Via Angler’s data API (API reference doc)

In this document we outline the steps involved to send flat file data via AWS S3. However, if you prefer to send data through data API, please let us know. We will create an API key for this data ingestion. Please note that this API key will be different from the front-end events API key.

Data Transfer via AWS S3

Please let the Angler team know the name and email address of the individual from the client side who will be sending data via ASW S3. Angler will create a dedicated bucket for the client (workspace). The individual will receive 2 emails from Angler AI : one with a public key and the other with a secret access key. Please do not share the secret access key with others. You will need the information in both the emails to transfer file(s). If you are going to use Cyberduck, Firezilla, or WinSCP to transfer files to Angler’s S3, please refer to this document.

Field Mappings

Angler’s standard commerce data spec for WooCommerce backend can be found here. Please use this document to map WooCommerce backend object fields to Angler’s standard commerce data spec. There are 4 main objects:

• Orders
• Customers
• Products
• Line Items

Orders and Customers objects are required, and the rest are strongly recommended. For WooCommerce fields, we are referencing this WooCommerce RestAPI docs.