BUILD VS USE
Build it yourself, or add one step.
HubSpot's help page suggests a custom setup for real deal values. Here's what that setup involves, so you can decide with the whole list in front of you.
Building it yourself
- API upgrades
- Logs
- Event IDs
- Retries
- Matching rules × 4
- Sign-in × 4
- Cloud project
Ledion
Send conversion
Ledion
| Build it yourself | Ledion | |
|---|---|---|
| Trigger | A webhook or code action in the workflow, plus a server to receive it | The Send conversion step |
| Google Ads | A Google Cloud project with Data Manager API access, and a service account or an OAuth app that passes Google's verification | Add Ledion's service account as a user in Google Ads |
| Meta | A Conversions API token, the CRM event format, and the 7-day limit | Paste the dataset ID and token |
| Microsoft Ads | An Entra app, a developer token, OAuth with refresh tokens that rotate, and goal names that must match exactly | Sign in with Microsoft and pick the goal |
| Conversions API v3, its required User-Agent format, and the 7-day limit | Paste the pixel ID and token | |
| Matching | Each network's email and phone rules, SHA-256 hashing, and picking the right contact on a deal | Done per network, from HubSpot data, at send time |
| Duplicates | A stable event ID per network, so retries and re-enrollments don't count twice | Built in. "Once per record" by default |
| Failures | Retries with backoff, Retry-After, and an alert when a token stops working | 7 attempts over about 9 hours, and an email when a connection needs you |
| Visibility | Logs you build and read yourself | An activity log, and a result per network in the workflow |
| Upkeep | API version changes (Meta ships a new one about every four months), deprecations, HubSpot's date-based API versions | Mine to keep current |
When building it yourself makes sense
You need one network, you have an engineer with time, and you already run servers with someone on call. Then
build it. If you'd rather spend that time on the ads, add one step.