- GoHighLevel connection
- How the product receives data from GoHighLevel (contacts, opportunities, payments): a documented native integration (app or OAuth), webhooks sent from GHL workflows, or a tracking script on pages only. Writing data into GHL is not receiving it.
- Sends GHL stage changes
- Whether a chosen GoHighLevel opportunity stage change (for example Booked or Qualified) can be sent to an ad platform as a conversion, and what has to be built per stage.
- Reads GHL payments
- Whether payments recorded in GoHighLevel (orders, invoices, transactions) reach the product as revenue, so a deposit and a later balance are both counted.
- What the bill scales with
- The usage measure the vendor's published pricing grows with, such as CRM contacts, tracked revenue, sessions, pageviews, visitors, events or ad spend.
- Lowest published paid plan
- The monthly price of the cheapest published paid plan that a GoHighLevel lead-gen or service business would buy, on the check date, with its billing term. When the vendor has separate ladders (ecom and lead gen, say), it is the lead-gen ladder. Free plans are covered by the trial row.
- Meta Conversions API
- Whether the product sends conversions to Meta server-side through the Conversions API, and on which plan.
- TikTok Events API
- Whether conversions are sent to TikTok server-side, whether the vendor calls it the Events API or server events to the TikTok pixel. Browser-only pixel events do not count.
- Dedupes with the browser pixel
- Whether the product documents deduplication between its server events and the same events from a browser pixel (shared event ids), so one sale is not counted twice.
- Choice of attribution model
- Whether reports can credit sales to campaigns under more than one documented model (for example first click, last click, linear).
- Revenue against ad spend
- Whether the product reports collected revenue next to ad spend from its own data, and at which level: the account total, campaign, ad (ad set and ad) or creative.