All Collections
Zapier Integration Setup
Zapier Integration Setup

Learn how to use Zapier to send events to Cometly from any application.

Updated over a week ago

👋 Start Here

Welcome to our guide on leveraging the power of our new Zapier integration with Cometly. Zapier allows you to automate the flow of data between thousands of applications and Cometly. Building a Zap in Zapier means you can send events from a large variety of applications.

There are two ways to send events to Cometly: Server and Browser.

Zapier sends server events to Cometly for actions that occur in your backend systems where Cometly doesn't have a direct integration.

Common Use Cases For Zapier

  • Form Submissions: As an alternative to placing a browser event on a thank you page after a website visitor submits a form, you can send a server event every time a form is filled out.

  • CRM Actions: For actions that occur in your CRM such as when a deal is created or when a deal is moved to Closed Won, you can send a server event to Cometly.

How It Works

The Cometly base code pixel automatically captures information on form submissions on your website. It captures the first name, last name, full name, email address, and phone number fields. When a server event is sent to Cometly from Zapier, the attribution algorithm will automatically match the email address used on the form submission and link to the visitors journey data.

If we receive the customer's email from a form earlier in the funnel, you can use Zapier to send just the email address to Cometly.

How to setup a Zap in Zapier

Learn the step-by-step process for creating a Zap in Zapier to send server events from any application to Cometly.

Important: Each space in Cometly has a different Zapier API Key. If you are setting up Zapier for multiple spaces, ensure that you have the connections organized in Zapier as shown in the video.

The Cometly Pixel Helper (Google Chrome Plugin) showcased in the video will help you determine if you are automatically capturing the email address on the form submission.

Use Cases

It's important to understand some use-case-specific requirements that ensure Cometly can effectively track customer actions:

For eCommerce Stores:

If the email address is not captured on the order form, you must include the customer's IP address, fingerprint, and comet_token. The email provides us the unique identifier for the customer, while the IP address, fingerprint, and comet_token ensures we can accurately track purchases. Cometly has a direct integration for all major Ecommerce stores and funnel softwares.

If you are using Zapier to send purchase events and you need a way to indicate that a purchase is an upsell.

For Standard Marketing Funnels / Backend System Actions:

If we receive the customer's email from a form earlier in the funnel, you can use Zapier to send just the email address to Cometly. Our system will automatically track that lead based on the script placed on your site. For tracking purchases, services like Stripe can send just the email, as we already have it captured from the funnel.


Using Webhooks by Zapier can be especially useful in situations where Zapier does not have a direct integration with a specific application or service.

Here are some key reasons why you would want to use Webhooks in such scenarios:

  1. Custom Integration: If Zapier doesn't support a specific app or service directly, Webhooks can act as a bridge. You can use Webhooks to send data from that unsupported app to Zapier, and then from Zapier to other apps. This allows for custom integrations with a wide range of services that might not be available in Zapier's standard integrations.

  2. Real-time Data Transfer: Webhooks provide a way to receive real-time data. Unlike typical APIs that require polling (regularly checking for data updates), Webhooks send data immediately when an event occurs. This makes them ideal for tasks that require instant updates or actions.

Did this answer your question?