Choose a delivery method.
Meta (Facebook Ads) and Google Sheets receive a direct sync. You upload the supplied audience files to Google Ads and LinkedIn. Other platforms that place ads across websites receive output files.
HubSpot and HighLevel workflows.
- Send records to HubSpot and HighLevel through automated workflows. Map company records and audience records to the objects your team uses.
- Choose a stable identity key, such as CRM ID or an agreed domain-and-email combination. Updates should resolve to the existing record.
- Map intent score, topic cluster and last activity into fields that routing and lifecycle rules can read.
- Apply agreed enrichment-confidence thresholds before records enter sales or campaign workflows. Enrichment is included with Starter, Growth and Enterprise.
Webhooks and exports for other systems.
A workflow webhook can send records to any system that accepts an HTTP request. Export is also available for CRMs and automation tools.
For each receiving system, assign an owner for field transformations, retries and schema changes. Keep record identifiers consistent across the handoff.
Audience refresh and consent.
- Set refresh windows around the sales cycle and the age of the underlying signals. Include a schedule for customer-uploaded audience files.
- Confirm the permitted customer-list identifiers and the applicable consent and platform requirements.
- Keep campaign tracking parameters and CRM stages aligned so outcomes can be traced to the activated audience.
Operate automated workflows.
- Plan approvals, branching or field transformations in the receiving system where your workflow requires them.
- Batch high-volume updates within destination limits.
- Record automation run IDs alongside CRM record IDs for troubleshooting.
- Manage token rotation with your security policy. Keep long-lived credentials out of browser code.
Design the workflow HTTP request.
| Decision | Implementation guidance |
|---|---|
| Transport | Use HTTPS for delivery. |
| Authentication | Agree a supported signature or bearer-token mechanism, rotation process and any appropriate network restrictions. |
| Duplicate handling | Use a stable event identifier and deduplicate before creating downstream records. |
| Acknowledgement | Return a successful status after the payload has been durably accepted. |
| Failure handling | Define backoff and retry behavior for server errors, with an owner and observable delivery history. |
Match the fields to the channel.
Use the field matrix before sending records to calling, email, direct mail or ads. A field useful for identity matching may require a different validation tier for direct contact.