Webhooks: Sending UTM and Ad Tracking Data

If you send leads into PloverCRM using a webhook, you can also send tracking details such as:

• UTM source
• UTM medium
• UTM campaign
• Google click ID
• Facebook click ID

This helps PloverCRM save where the lead came from.

Important #

If you want PloverCRM to save this tracking data automatically, you should use the expected field names.

For example, these should be sent inside plover_crm_cookies:

• plover_crm_utm_source
• plover_crm_utm_medium
• plover_crm_utm_campaign
• plover_crm_utm_term
• plover_crm_utm_content
• plover_crm_gclid
• plover_crm_fbclid

Recommended webhook fields #

You can send these extra fields with your webhook:

• plover_crm_current_url
• plover_crm_referer
• plover_crm_user_ip
• plover_crm_user_agent
• plover_crm_cookies

Example #

Can I use my own field names? #

Yes, but only for normal field mapping.

If you use your own field names, you can still map them manually inside your PloverCRM data source setup.

But if you want PloverCRM to detect and save tracking details automatically, use the expected field names shown above.

Facebook and Google ad details #

If you also want to send Facebook or Google ad details, you can include them as normal webhook fields and map them manually.

Examples:

• _meta_campaign_name
• _meta_ad_name
• _google_campaign_id
• _google_adgroup_id
• _google_gcl_id

Simple rule #

• Use PloverCRM field names for automatic tracking
• Use your own field names if you plan to map them manually