Cometly call tracking integration
Send your calls to Cometly, each tied to the visitor its pixel saw on your site, so your ad attribution counts the leads that phone.
Cometly call tracking integration
What is Cometly call tracking with Nimbata?
Nimbata's Cometly call tracking integration sends each inbound call to Cometly as a contact event, with the visitor IDs Cometly's pixel set on your site, so Cometly ties the call to the same visitor and the ads that brought them.
Nimbata's dynamic number insertion reads Cometly's comet token and fingerprint from the visitor's session, and a Nimbata workflow decides which calls reach Cometly, from first-time callers to the calls Nimbata AI marks as leads. Each event carries the caller's name and phone, the visitor's IP and the time of the call. No value or revenue is sent, and calls with no Cometly visitor data are skipped. See call attribution for how Nimbata ties each call to its source.
From Nimbata
Into Cometly
- Call activity
Event, contact, Event time, Caller's phone
- Marketing attribution
Comet token, Fingerprint, Visitor's IP
- Call intelligence
Caller's first and last name
Events
contactNimbata · inbound call
Matched visitorEvent
- Event name
- contact
- Event time
- 9:41 AM, the call's start
- Phone
- +1 312 555 0148
Visitor
- Comet token
- From the pixel
- Fingerprint
- From the pixel
- IP address
- The visitor's
Contact
- First name
- Jordan
- Last name
- Miller
In Cometly
See every call in Cometly
An event from Nimbata, as it arrives in Cometly. Everything numbered came from Nimbata.
Events
contact
- Comet token2
- From the pixel
- Fingerprint2
- From the pixel
- IP address2
- The visitor's
- First name3
- Jordan
- Last name3
- Miller
- Phone3
- +1 312 555 0148
1Call events
Every call becomes a contact event
When a workflow sends a call, Cometly gets one contact event for it, with the time of the call.
2Attribution
The same visitor the pixel saw
The comet token and fingerprint come from Cometly's own pixel on your site, so the call is tied to that visitor and the ads they came from.
3Caller
Who called
The caller's name, split into first and last, and their phone number go with each event.
Automation
Send Cometly the calls that are leads
Test it. AI checks the call first. A lead goes to Cometly as a contact event, a call that isn't one is never sent, and the caller's history decides whether sales hear about it or the call is logged in HubSpot.
A workflow, top to bottom: when a call ends, AI analyzes it and checks whether it is a lead. Not a lead, the call is tagged and never sent to Cometly. A lead goes to Cometly. Then the caller’s history decides: a new caller’s lead alerts #sales in Slack, a repeat caller’s call is logged on their HubSpot contact. Test it with the choices beside it.
Test this workflowSandbox
Run log
- Call ended, 4m 12s9:41:02
- AI: appointment booked, value $4809:41:05
- AI: qualified lead, value $9009:41:05
- AI: a sales pitch, not a lead9:41:05
- Tagged “Not a lead”, not sent9:41:06
- Cometly: contact event sent9:41:06
- First call from this number9:41:06
- Called before, twice this month9:41:06
- Slack: #sales alerted, caller and source9:41:07
- HubSpot: call logged on the contact9:41:07
What you can do with Cometly
More than a call count. Nimbata ties each call to the visitor Cometly already knows and decides which calls it sees.
01Tied to the visitor the pixel saw
Cometly's pixel identifies the visitor on your site. When they call your Nimbata number, the event carries that visitor's comet token and fingerprint.
02AI decides what counts
Ask Nimbata AI a question about the call, and only the calls it says yes to reach Cometly.
03The caller, by name
Nimbata splits the caller's name into first and last and sends it with their phone number.
04Only calls Cometly can match
Calls with no Cometly visitor data, such as calls to offline numbers or call assets, aren't sent. They're logged as skipped.
05A check on your tracking script
The Cometly code has to be in your Nimbata tracking script. If it isn't, Nimbata warns you to republish the script.
How it works
Connect Nimbata to Cometly in three steps
No code. Paste your Cometly URL, republish your tracking script, and pick which calls count.
Paste your Cometly URL
Choose Cometly under Integrations and paste your Cometly URL. There's no sign-in or API key, and the Test button sends a test event.
1Connect
Republish your tracking script
Your Nimbata tracking script needs the Cometly code. If it doesn't have it yet, Nimbata warns you to republish it.
2Publish
Pick which calls go
Add Cometly to a workflow step and give it conditions, such as first-time callers, calls over a minute, a source, a tag, or an answer AI found on the call.
3Choose
Customers
Trusted by marketers who need better attribution
Teams use Nimbata to see which calls make money and to settle questions about lead quality.
50%More conversionsnovi.digital
“With Nimbata, we can see which phone calls make money and reinvest away from the ones that don’t.”
4.5xGrowthService24
“Before Nimbata, everything was manual CPC. Every day was a new battle. Now, the algorithm knows exactly which jobs bring more money.”
200+Phone conversions a monthSkyleads
“When clients question lead quality, I just play the call recording. No more debate.”
Everything you need to know about Nimbata + Cometly
What does the Nimbata + Cometly integration do?
It sends your inbound calls to Cometly as contact events, each tied to the visitor Cometly's pixel identified on your site, so Cometly can count the call for the ads that brought that visitor. A Nimbata workflow decides which calls are sent.
How do I connect Nimbata to Cometly?
Open Integrations in Nimbata, choose Cometly and paste your Cometly URL. There's no sign-in or API key, and a Test button lets you send a test event. Your Nimbata tracking script must include the Cometly code; if it doesn't, Nimbata warns you to republish it. Then add Cometly as a step in a workflow.
What does Nimbata send to Cometly?
One event per call, named contact, with Cometly's own visitor IDs from its pixel (the comet token and fingerprint), the caller's first and last name, split from the caller name, their phone number, the visitor's IP and the time of the call.
How does Cometly know which visitor called?
Cometly's pixel identifies each visitor on your site. Nimbata reads the comet token and fingerprint it set and sends them with the call, so Cometly ties the call to that same visitor.
Does Nimbata send a value or revenue to Cometly?
No. The event carries no value or revenue, and there are no fields to choose; every event has the same fields.
Are all calls sent to Cometly?
No. Calls with no Cometly visitor data, such as calls to offline numbers or to a number on a call asset, aren't sent, and they're logged as skipped.
Can I choose which calls reach Cometly?
Yes. Cometly is a step in a Nimbata workflow, so you set its conditions, such as call outcome, duration, first-time callers, source or campaign, tags, value, or an answer Nimbata AI found on the call. The step itself has no settings.
Does it work for forms, outbound calls and texts?
No. Only inbound calls are sent to Cometly. Form submissions, outbound calls and texts aren't.
Does Nimbata send recordings, transcriptions or AI summaries to Cometly?
No. Each event carries only the visitor IDs, the caller's name and phone, the IP and the event time.
What happens if an event fails to send?
Nimbata sends each call when the workflow runs, with no retry, and doesn't email you if the connection stops working. On the Agency plan and the trial, the Integration Events log shows every attempt, with your Cometly URL hidden.
Which Nimbata plans include the Cometly integration?
The Pro, Marketing and Agency plans, and the 14-day free trial. See pricing for everything else each plan includes.
Still unsure? Talk to a human
Your next call belongs in Cometly.
Connect Cometly and tie every call to the visitor and the ads that brought it.
- 14-day free trial, no credit card
- Billed per answered call
- 24/7 expert support
- No long-term contracts
Nimbata + Cometly
Part of Integrations