Video Walkthrough
Description
The WhatsApp Conversions API (CAPI) allows you to send customer events (e.g., leads, purchases, subscriptions) directly from your server or Datahash to Meta’s Business Manager. This ensures more reliable conversion tracking, especially when browser-side signals are blocked or lost.
Pre-requisites
- Facebook Business Manager account with Pixel access.
- A Dataset ID and Access Token (if setting up manually).
- A Datahash account with access to configure destinations.
Getting Started
- Go to Datahash Studio.
- Enter your credentials to log in.
- Navigate to the Meta category under Destinations.
- Click on the WhatsApp Conversions API connector tile.
- Now you can implement the connector either by Single Sign in or adding manually.
Setup Methods
Option 1: Single Sign-On (SSO)
- Choose the Business Account you want to integrate.
- Select the Pages you want to provide access to.
- Grant access permissions.
- Provide a Connection Name.
- Select the Facebook Page you want to integrate.
- Select the Dataset ID associated with that page.
- Click Finish.
- Setup is now complete and added to your dashboard.
Option 2: Manual Setup
- Provide the Dataset ID and Access Token.
- Click Validate Credentials.
- Once validated, click Finish.
- Setup is now complete.
Finding Pixel ID and Access Token
- Log in to Facebook Business Manager.
- Select the appropriate Business Account.
- Go to the Settings tab.
- Under the Pixel ID section, locate your Pixel ID.
- Scroll to Conversion API and click Set up manually.
- Click Generate Access Token to retrieve your token.
- Enter the Pixel ID and Access Token in the Datahash dashboard.
- Click Close.
Sharing Access with Datahash
- In Meta Business Manager, go to Business Settings
- Under Users, click People.
- Click Add.
- Enter the email: analytics@datahash.com.
- Enable Employee Access → click Next.
- Under Assign Access, go to Pixels.
- Select your Pixel → enable Employee Access.
- Click Invite.
QA & Implementation Process
- Pre-implementation QA → Datahash validates setup.
- Publish GTM → Clients publish changes in GTM.
- Post-production QA → Datahash verifies events.
- Handover → Implementation is closed with a handover doc.
Standard Events Mapping
Datahash automatically maps Neotag event names to Facebook Standard Events:
| Neotag Event Name | Facebook Standard Event |
| neotag.page() | PageView |
| view_item | ViewContent |
| add_to_wishlist | AddToWishlist |
| add_to_cart | AddToCart |
| subscribe | Subscribe |
| submit_application | SubmitApplication |
| start_trial | StartTrial |
| search | Search |
| schedule | Schedule |
| purchase | Purchase |
| lead | Lead |
| begin_checkout | InitiateCheckout |
| find_location | FindLocation |
| donate | Donate |
| customize_product | CustomizeProduct |
| contact | Contact |
| complete_registration | CompleteRegistration |
| add_payment_info | AddPaymentInfo |
Notes:
- For Purchase, properties.currency is required.
- For Search, the query must be a string.
- If currency is not provided in Order Completed, default = USD.
Custom Events
- Any unmapped events are sent as Custom Events.
- Properties must align with Facebook’s event requirements.
Deduplication
Since events can come via both Pixel (browser) and CAPI (server), deduplication is applied.
Events are deduplicated when:
- Same Pixel ID.
- Same event_name (e.g., Purchase).
- Same event_id (e.g., Order ID).
Connect to Sources:
Facebook’s CAPI Destination can be connected to various platforms such as websites, marketing automation tools, warehouses, apps, and ecommerce stores through Event Streams and Cloud Apps. The eligible sources include Website/JavaScript SDK, App, Ecommerce Stores (Shopify, WooCommerce), Big Query, Moengage, Braze, and Clevertap.
Web Sources:
- Website/JavaScript SDK
- App
- Ecommerce Stores (Shopify, WooCommerce)
