How to Set Up Ad Conversion Actions in Workflows

Created by PX Marketing, Modified on Tue, 19 Aug at 5:01 PM by PX Marketing

Overview

PXME allows you to send offline conversion events (form fills, purchases, calls, chat replies, etc.) directly into Google Ads. This ensures your campaigns can optimize effectively based on real results rather than just clicks. Proper setup involves creating a conversion action in Google Ads, then mapping that action inside PXME workflows.


Step 1: Create a Conversion Action in Google Ads

  1. Go to Google Ads > Tools & Settings > Conversions.

  2. Click + New Conversion Action.

  3. Depending on your Google Ads interface:

    • Older Version: Choose CRMs, files, or other data sources, then select Skip this step and set up later.

    • New Version: Choose Track conversions from clicks.

  4. Select the type of conversion (Google Analytics, Salesforce, third-party app analytics, clicks, or calls).


Step 2: Configure the Conversion Goal

  • Set the Primary Goal to Converted Lead.

  • In the new Ads interface, this appears under Conversion Action Settings.


Step 3: Name and Configure the Conversion

  1. Enter a Conversion Name (example: Click).

    • ⚠️ This name must match exactly when you set it in PXME.

  2. Set a Value (optional).

  3. Set Count to One (recommended).

  4. Adjust attribution:

    • Click-through window: 90 days

    • Attribution model: First Click

  5. Click Done to save.


Step 4: Add Conversion Actions to PXME Workflows

PXME supports the following triggers:

  • Form Submissions

  • Order Purchases

  • Survey Submissions

  • Incoming Calls (via Number Pool)

  • Chat Widget Replies

Example: Form, Order, or Survey

  1. In PXME, create a Workflow.

  2. Add the trigger: Form Submission, Order Form Submission, or Survey Submission.

  3. Apply a filter to select the correct form/order/survey.

  4. Add the action: Add to Google AdWords → Select Other.

  5. Enter the exact Conversion Name from Google Ads.

    • PXME validates spelling/casing to prevent errors.

Example: Incoming Call via Number Pool

  1. Create a workflow with trigger: Call Status.

  2. Add filters: Direction = Incoming + select the Pool Number.

  3. Confirm the pool number script is installed in your funnel/website header.

  4. Add the action: Add to Google AdWords → Select Other.

  5. Enter the exact Conversion Name.

Example: Chat Widget

  1. Create a workflow with trigger: Customer Replied.

  2. Add the action: Add to Google AdWords → Select Other.

  3. Enter the exact Conversion Name.


Step 5: Timing & Attribution

  • After a contact comes in with UTM + gclid/wbraid/gbraid, PXME syncs to Google Ads within 15–20 minutes.

  • Conversion uploads to Google within ~5 minutes after execution (instead of 24 hours).

  • You should see conversions appear in Google Ads in about 10 minutes.


Google Ads Conversion Flow in PXME Ad Manager

  • Navigate to Marketing > Ad Manager > Settings > Google Ads > Conversions.

  • You can create or edit offline conversion actions directly inside PXME.


Meta Conversion Dataset Support

  • PXME now supports multiple datasets (instead of a single pixel).

  • Navigate to Ad Manager > Settings > Meta > Conversions tab.

  • Click + Create new dataset, name it, select goal type, and generate a Dataset ID & Pixel Code.


FAQs

1. How do I confirm it’s working?
Check the workflow action’s History tab. If executed successfully, the conversion will appear in Google Ads within ~10 minutes.

2. Does this work with all triggers?
No. Supported triggers are: Form Submissions, Order Purchases, Survey Submissions, Incoming Calls (Number Pool), and Chat Widget Replies.

3. Why must the conversion name match exactly?
Google Ads requires exact spelling and casing to match conversions. Any discrepancy will cause failure.

4. What’s the benefit of the new 5-minute sync?
It shortens the feedback loop, helping campaigns optimize faster and reducing conversion delay issues.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article