Scaling In-Person Event Registration: One ClickDimensions Widget to Rule Them All

1) This solution is for

When you are hosting physical, in-person events, you don't have a native Zoom or Teams connector automatically creating your Dynamics 365 Event Participations.

This pattern lets you embed a single ClickDimensions form widget across all your local event landing pages, then use Power Automate + utm_content to dynamically route attendees to the correct in-person Event record in Dynamics 365.

2) When to use it (and when not to)

Use it when:

• You are running a physical event series (roadshows, local mixers, in-person training) and need people linked to specific Dynamics Event records.
• You want to maintain exactly one "Master Registration" form instead of cloning a new one for every city.
• Your web team can embed the form as a Widget (not an iframe) and append query strings like ?utm_content=... to the URLs.

Don’t use it when:

• You are running a standard virtual webinar (use the native ClickDimensions webinar integrations).
• The website forces an iframe embed (the form can’t reliably read the parent page URL query string).
• You need a complex, multi-ticket physical checkout system.

3) Pre-flight checklist (what must be true before you click Run)

Before building the flow, confirm all of these are true:

• Embed method: Your ClickDimensions Web Content record is published and embedded using the Widget script.
• URL pattern: Each in-person event page has a unique parameter.
  Example: .../dallas-mixer?utm_content=mixer-dal-2026
• Dynamics setup: Your Event table has a custom text field (for example, Event Key) that matches those URL values exactly.
• Click mapping: Your form includes a hidden field physically mapped to the UTM Content global parameter in the Click designer.
• Power Automate: You have permission to create Event Participation records, and your flow starts with a 1–2 minute delay.

4) Step-by-step (test small first)

Step A — Choose your Event Key convention

Pick a clean, dash-separated format for physical events.

Examples:

• bootcamp-austin-2026
• bootcamp-seattle-2026

Step B — Prep the Dynamics Event + Website

1. Enter bootcamp-austin-2026 into the Event Key field on your Austin Event record.
2. Ask the web team to place the Click Widget script onto the Austin landing page.
3. Test small first: Open the page in Incognito and submit a test registration:
   yoursite.com/austin-bootcamp?utm_content=bootcamp-austin-2026

Verify after test submit

• Check Dynamics / Click posted form data and confirm the utm_content value was actually captured.

Step C — Build the Flow

Suggested flow pattern

1. Trigger: When a row is added (Click Form Submission / Posted Form)
2. Delay: 1 minute
   (Click data can arrive in waves; give the UTM field time to sync)
3. Get Web Content: Confirm the submission came from your Master Registration form
4. List Rows (Events): Query the Event table where Event Key = utm_content from the submission

Step D — The Safety Gate (do not skip this)

1. Condition: Did you find exactly one Event?
   • If No → terminate the flow (don’t guess)
2. Duplicate check: List existing Event Participations to see if this Lead/Contact is already registered for that Event
3. Create Event Participation: Only if no duplicate exists, link the Event to the person

Future You will thank you when you don’t have to manually delete duplicate name badges before printing.

5) Common gotchas (the stuff that burns consultants)

The iFrame trap

If you embed the form as an iframe instead of a Widget, the form often cannot read the utm_content value from the browser URL. Result: nothing populates.

The “clean URL” redirect

If marketing uses a link shortener or redirect that strips query parameters before the page loads, your flow is flying blind.

Naming vs mapping

Adding a form field labeled “UTM Content” is not enough.
You must configure the actual UTM mapping in the Click field properties.

Blank lookup crashes

If the submission fails to link to a Contact or Lead, the “Create Participation” step can fail when it tries to use a null GUID.

Fix: Add a condition to verify the Contact/Lead ID exists before creating the participation record.

Consultant law #12: The one time you skip the duplicate check is the exact time someone clicks Submit four times because the coffee shop Wi-Fi is slow.

6) Validation checklist (how you prove it worked)

Run this checklist after your test:

-The Capture: The Posted Form record shows the correct utm_content value -The Match: The Power Automate run successfully found the matching in-person Event ID -The Roster: The attendee appears in the Event Participations subgrid/view on the Event record -The Bouncer: Re-submit as the same person and confirm the duplicate check prevents a second participation record

7) Real scenario (short, specific, relatable)

Your client is running a 10-city Executive Breakfast Tour. Because these are physical, in-person events, there is no webinar integration to automatically create Event Participations.

Instead of building and managing 10 separate ClickDimensions forms, you embed one “Breakfast RSVP” Widget on all 10 city landing pages.

Examples:

• Miami page URL: ?utm_content=breakfast-mia
• Chicago page URL: ?utm_content=breakfast-chi

When an executive RSVPs on the Chicago page, Power Automate reads the key, finds the Chicago Event record in Dynamics, and creates the matching Event Participation record.

Result: Marketing gets one reusable form, and field teams get clean, city-specific attendee lists in Dynamics.

Quick summary (why this pattern works)

• One form for many physical event pages
• utm_content acts as the routing key
• Power Automate links submissions to the right Event
• Duplicate checks keep participation records clean
• Validation checklist proves the automation works before rollout