- 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.
- Google Ads offline conversions
- Whether CRM conversions are sent to Google Ads as offline click conversions or enhanced conversions for leads.
- 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.
- Per-event delivery log
- Whether you can inspect each event the product sent to an ad platform: the payload, the destination and the platform's response or error (an outbound log). A log of the events the product received is an inbound log and answers a different question.
- Sends hashed customer details
- Whether server events include hashed customer identifiers (email, phone, name) so the ad platform can match them to people. Sent is not the same as matched.
- Choice of attribution model
- Whether reports can credit sales to campaigns under more than one documented model (for example first click, last click, linear).
- 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.
- 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.
- Setup help
- Whether the vendor publishes done-for-you or guided setup, and whether it is included or paid.