Skip to main content

Meta and Google Ad Tags & Details

When someone clicks a Meta (Facebook / Instagram) Click-to-WhatsApp ad or a Google Click-to-WhatsApp ad and sends you a message, GoGHL automatically:

  1. Tags the contact so you can instantly identify ad leads.
  2. Appends all available ad metadata (campaign, adset, ad, source, media links, etc.) to the end of the first WhatsApp message inside GoHighLevel.

This makes it easy to:

  • See exactly which ad generated the lead.
  • Build workflows and automations based on the ad source.
  • Attribute revenue and results back to campaigns without extra tools.

✅ This feature works automatically for Meta Ads (Facebook & Instagram) and Google Ads that use Click-to-WhatsApp.

What Gets Added?​

1. Contact Tags (Meta Ads)​

For Meta Click-to-WhatsApp leads, we automatically add:

  • instagram-ad-lead-whatsapp – when the lead comes from an Instagram ad.
  • fb-ad-lead-whatsapp – when the lead comes from a Facebook ad.

You can use these tags in:

  • Smart lists
  • Workflows
  • Pipelines / Opportunities
  • Reporting & segmentation

💡 Example: Build a workflow that triggers only for fb-ad-lead-whatsapp and sends a specific follow-up sequence.

2. Ad Details Appended to the Message​

Along with the lead’s message (for example:

“Hola, me interesa el tratamiento Plasma IQ”)

we append the ad payload we receive from Meta / Google directly into the same WhatsApp message in GHL. It looks conceptually like this:

Hola, me interesa el tratamiento Plasma IQ

sourceApp: facebook
sourceType: ad
sourceId: 1234567890
campaignName: Plasma IQ Lead Gen – MX
adSetName: Lookalike 1% – Women 25–45
adName: Video Test 3 – Hook A
mediaType: VIDEO
mediaUrl: https://facebook.com/...
renderLargerThumbnail: true
showAdAttribution: true
...

⚠️ The exact keys/fields depend on what Meta/Google send. We simply forward and append everything we receive, so you don’t lose any attribution data.

You can then:

  • Read this info directly inside the Conversations tab.
  • Use it in workflows via custom fields, regex, or parsing steps.
  • Store key values in custom fields for deeper reporting.

Where Do I See This in GoHighLevel?​

  1. Open the relevant Location in GoHighLevel.
  2. Go to Conversations.
  3. Open a conversation that originated from a Meta or Google Click-to-WhatsApp ad.
  4. Look at the first incoming message from the lead.

At the bottom of the text, you will see the appended block containing:

  • Source app (facebook, instagram, google)
  • Campaign / ad / adset identifiers (when provided)
  • Media info (type, URL)
  • Other metadata sent by the ad platform

How to Use This Data in Workflows​

Because the ad info is part of the message content and tags are added to the contact, you can automate based on:

1. Tags​

Example: Workflow that triggers only for ad leads.

  • Trigger: Contact Tag Added → fb-ad-lead-whatsapp OR instagram-ad-lead-whatsapp

  • Actions:

    • Create Opportunity in a specific pipeline
    • Assign to a sales rep
    • Send a tailored follow-up sequence
    • Notify your team in Slack/Email/WhatsApp

2. Message Content Parsing​

If you want more advanced logic (per campaign/adset/ad):

  1. Use a workflow triggered on conversation message / WhatsApp received.

  2. Parse the message body using:

    • Webhook → external parser (n8n, Make, Zapier, etc.)
    • Custom code / regex step (if available in your setup)

  3. Store parsed values (e.g. campaignName, adName) into custom fields.

  4. Branch your workflows based on those fields.

💡 Example: If campaignName contains Retargeting, send a shorter, urgency-based follow-up. If campaignName contains Cold Prospecting, send a longer intro nurturing sequence.

Do I Need to Turn Anything On?​

No extra toggle is required on the GoGHL side.

Requirements:

  • Your Meta or Google campaign must be configured as Click-to-WhatsApp.

  • The WhatsApp number used in the ad must be connected via GoGHL.

  • Once the lead sends a message, we handle:

    • Tagging the contact (instagram-ad-lead-whatsapp / fb-ad-lead-whatsapp).
    • Appending the ad metadata to the first incoming WhatsApp message.

Best Practices​

  • Name your campaigns clearly Use meaningful names in Meta/Google (e.g. MX | Plasma IQ | IG Story | Warm) so when they show up in the message, your team can understand at a glance.

  • Create dedicated workflows per source Example:

    • Facebook ad leads → Sales pipeline A
    • Instagram ad leads → Social DMs team
    • Google ad leads → Phone call follow-up team

  • Use tags for routing Combine fb-ad-lead-whatsapp / instagram-ad-lead-whatsapp with your internal tags (hot-lead, consult-booked, etc.) to keep your CRM organised.

FAQ​

Does this work for both Facebook and Instagram?​

Yes. For Meta Ads, we differentiate using tags:

  • fb-ad-lead-whatsapp → Facebook
  • instagram-ad-lead-whatsapp → Instagram

Both are Click-to-WhatsApp ads handled via GoGHL.

Does this work for Google Ads?​

Yes, for Google Click-to-WhatsApp ads where Google passes metadata to us. We attach any ad data we receive to the first WhatsApp message, just like with Meta.

Can I turn this feature off?​

Currently, this feature is designed to always be on so that you never lose attribution data. If you strongly prefer not to append ad info, please contact support and we can discuss options/workarounds.

Can I store the ad fields in custom fields automatically?​

Out of the box, we append all data to the message body. To store values like campaign/ad name in custom fields, we recommend:

  • Using workflows + webhooks, or
  • An external automation tool (e.g., n8n, Make, Zapier) to parse and map fields.

We’re exploring native mapping options based on user demand.

Does this work for organic WhatsApp messages?​

No. Tags and ad details are only added when messages originate from Meta / Google Click-to-WhatsApp ads. Organic conversations or direct messages will not receive these tags or metadata.

Let's connect