Receive Calendly events
Bring the scheduled-event and invitee payload into Adscriptly through a mapped webhook payload or a Zapier workflow you control.
Calendly + Google Ads
Webhook or ZapierScheduling
Turn the right Calendly booking into a Google Ads conversion.
Use a Calendly scheduling webhook or Zapier trigger, choose the event type and booking state that count, preserve the supported click identifier captured with the invitee, and review the Google Ads conversion action.
C
Source
Calendly
GA
Destination
Google Ads
Intended outcome
Optimize toward selected booked meetings instead of counting every scheduling-page visit as equal.
Connection scope
This route qualifies scheduling events. It does not change Calendly availability, routing forms, event types, or calendar records.
What the connection does
Choose which Calendly events to send to Google Ads.
Choose the meeting type
Require the Calendly event type, booking status, or mapped invitee answer that represents the qualified meeting.
Preserve booking attribution
Carry the supported Google Ads click identifier captured before or during scheduling into the event payload.
Review the Google Ads output
Choose the Google Ads account and conversion action, inspect the mapping, and test the external handoff before enabling it.
Data flow
Know what moves between systems.
CalendlyAdscriptly logicGoogle Ads
Calendly
Calendly event and invitee state
Adscriptly logic
Event-type and booking-state check
Google Ads
Booked-meeting conversion
Calendly
Event type, status, and invitee answers
Adscriptly logic
Selected booked-meeting condition
Google Ads
Eligible meeting outcome
Calendly
Invitee click-identifier field
Adscriptly logic
Connect the booking to the original click
Google Ads
Google Ads booked-meeting conversion
Calendly
Scheduled event and invitee ID
Adscriptly logic
Stable event identity and duplicate handling
Google Ads
Invitee-backed conversion record
Setup
Set up and test the Calendly event route.
- 01
Choose a Calendly trigger
Start with the invitee created, canceled, or rescheduled event that represents the business outcome you want to route.
- 02
Send a test payload
Use Zapier or your webhook sender to deliver representative fields, including invitee click-identifier field when attribution depends on it.
- 03
Map the qualification rule
Choose the accepted event type and booking status. Keep records that do not meet the rule out of the advertising signal.
- 04
Review the Google Ads destination
Confirm the account, conversion action, event timestamp, and value rule before the external handoff is enabled.
Connection controls
Review the connection method, event rule, and destination.
- The connection uses a mapped webhook or Zapier route; it is not a native source integration.
- Calendly must send the fields used by the mapping.
- A meeting needs the supported attribution field before it can be tied to a Google Ads click.
- The Google Ads destination is reviewed before the handoff is enabled.
Related integrations
Integration FAQ
Before you connect.
How does the Calendly Google Ads integration work in Adscriptly?
Adscriptly receives a mapped Calendly event through a webhook or Zapier, applies the configured rule, and prepares the eligible outcome for the selected Google Ads destination.
What must Calendly send?
The payload must include the event fields used for qualification and a stable event identifier. When click-level attribution is required, it must also include the supported identifier captured before the handoff.
Can canceled or rescheduled meetings be excluded?
Yes, when the event contract and rule include the relevant booking state. Define which states count before enabling the external handoff.
Does Adscriptly change records in Calendly?
No. This route receives the mapped event for qualification and delivery. It does not edit the source record, workflow, audience, catalog, or storefront configuration.
Calendly + Google Ads
Send a selected Calendly event to Google Ads.
Choose the trigger, send a representative payload, map the rule, and review the destination before enabling the external handoff.
