Skip to main content
Report Invoca phone calls and Signals to Pinterest as standard events, and use Invoca data to build site visitor audiences for targeting.

​
Step 1: Get your Pinterest Ad Account ID and Access Token

  1. Log in to your Pinterest Business account and go to Ads > Overview.
  2. Click the “Viewing: <Ad Account Name>” menu and find the account you want to integrate. Copy the ID under the account name.
  3. Go to Ads > Conversions, click Conversion access token in the left navigation, and click Generate new token. Copy the value.
  4. Decide which Pinterest event name you’ll use for each Call or Signal you want to report — you must use one of Pinterest’s standard names: add_to_cart, checkout, custom, lead, page_visit, search, signup, view_category, or watch_video. Only lead, signup, add_to_cart, and checkout can be used as a conversion objective for automated optimization.

​
Step 2: Configure Invoca to capture the Pinterest Click ID

By default, Invoca reports events to Pinterest using the hashed phone number as the primary match identifier. Capturing the Pinterest Click ID as well increases attribution accuracy.
  1. In Invoca, click the gear icon, then Marketing Data. Confirm there isn’t already a field with API Partner Name epik, then create one:
    • Type: Short text
    • Partner API Name: epik
    • Friendly Name: Pinterest Click ID
    • Attribution Model: Last
  2. Click the gear icon, then Invoca Tags, and find the Tag on your website.
  3. Open the Revision History tab and create a new draft, or continue an existing one.
  4. Find the Pinterest Click ID parameter in the Marketing Data section, set Data Source Type to Cookie, enable it, and enter _epik as the Data Source Name.
  5. Test your changes, then click Save & Go Live.

​
Step 3: Set up the integration in Invoca

  1. In the sidebar, click Integrations, then Manage Integrations.
  2. Click the Pinterest tile. Enter a friendly name and the Ad Account ID and Access Token from Step 1.

​
Create an Action

  1. Enter a friendly name for the Action (include “Call” or the Signal name to distinguish Actions).
  2. Optionally filter by Profile or Campaign.
  3. Under Triggered By, choose All Calls or Signal.
  4. Enter the Pinterest Event Name — it must exactly match one of the standard event names, matching the Triggered By selection from Step 1.
  5. Optionally enter a 3-letter currency code; leave blank to default to USD.
  6. Click Save. Repeat for each transaction type you want to report.

​
Validate that events are reaching Pinterest

  1. In Invoca, click Integrations, then Manage Integrations.
  2. Click the Pinterest tile, then the name of the Action you created.
  3. Review the Delivery Details chart, showing successes (green) and errors (red) by day for the last 30 days. Click Delivery History for individual requests and responses.
  4. In Pinterest, go to Ads > Conversions > Event history to confirm your configured events show an ingestion source of “Api.”

​
FAQs

Can I create audiences based on Invoca Events? Yes — see Pinterest’s documentation on building Site Visitor audiences filtered for API events. Does Invoca pass value and currency for Invoca Events? Yes — the Invoca Revenue field is sent as the value, defaulting to USD unless you set a different 3-letter ISO 4217 currency code in the Action. What fields does Invoca pass by default? The hashed Caller ID (SHA256, as the primary match identifier), event name, transaction ID (as the unique/de-duplication event ID), the Invoca Revenue field as value, currency, and the Pinterest Click ID. How can I see the data Invoca sends to Pinterest? Open an Action’s Delivery History tab and expand a row to see exactly what was sent for that call or Signal. How does Invoca send data to Pinterest? Invoca uses the Pinterest Conversions Events API. How do I update the integration if the person who set it up leaves the company? Generate a new Conversion Access Token in the same Pinterest Ad Account, then open the Pinterest integration tile in Invoca, click Edit, replace the old Access Token, and save — then monitor Delivery History for successful deliveries.

​
Where to go next

Last modified on September 25, 2026