InnerShift360 SOP Central

Dating ID Quiz GHL Automation Setup

Chiara — this SOP walks you through building the GoHighLevel automation for the Dating ID Quiz. The quiz page and the GHL form are already done. Your job starts at the automation layer. Follow the steps in order. Do not skip the testing section.

Your Mission

When someone completes the Dating ID Quiz and submits the form, GHL must capture the contact, save their result, apply the right tags, and send the right follow-up message — automatically.

Read This First

Chiara — Start Here

Before you touch anything in GHL, read these five points. They will save you 30 minutes of confusion.

  1. The quiz already works. You are not building the quiz, the form, or the website page. You are only building the GHL workflow that runs after the form is submitted.
  2. The form is named "Dating ID Quiz Result Capture." If you see a similar-looking form with a different name, do not use it. Ask before you proceed.
  3. The five result names must be exact. Discerned, Optimist, Performer, Protector, Distance Keeper. Two words for Distance Keeper. No hyphens. No "The." Capital first letters only.
  4. Test before you publish. All five results must be tested individually. If you only test one and publish, the workflow is not done.
  5. If anything is unclear, stop and message James. Do not guess on field names, tag names, or result spellings. One typo will break the whole branch.
Quiz Page
Dating ID Quiz

https://innershift360.com/dating-id-quiz/

GHL Form Name
Dating ID Quiz Result Capture

Form ID: oEaZHuklv7xBTqXYNY41

Form URL
Embedded Result Form

https://api.leadconnectorhq.com/widget/form/oEaZHuklv7xBTqXYNY41

Do you need a capture page?
No

The capture happens on the quiz result screen. No redirect. No separate page.

1. Overview 2. Before Building 3. Build the Workflow 4. If/Else Branches 5. Messages 6. Testing 7. Final Check Prompt 8. Reusable Template

1. What This Automation Must Do

The Dating ID Quiz lives on the website. When someone finishes the quiz, they see their result and an embedded GHL form appears. The website passes the result into that form using hidden fields. After the visitor submits the form, your workflow takes over.

Important: You are not building a landing page or a capture page. You are only building the workflow that runs when the form is submitted. Everything before the form is already built and working.

Every Piece You Need, In One Place

PieceExact ValueWhy It Matters
Quiz Pagehttps://innershift360.com/dating-id-quiz/The visitor takes the quiz here and submits the GHL form here.
GHL Form NameDating ID Quiz Result CaptureThis is the exact form your workflow will listen for.
Dating ID Source valuedating-id-quizTells GHL the lead came from this specific quiz.
Hidden Result ParameterresultPasses the result into the GHL custom field "Dating ID Result."
Hidden Source ParametersourcePasses the source into the GHL custom field "Dating ID Source."
Hidden Date Parametersubmitted_datePasses the submission date if the field is active.

The Five Dating ID Results — Memorize These

The workflow must use these five exact values. Do not rename them. Do not add hyphens. Do not pluralize. Do not add "The."

Discerned
Optimist
Performer
Protector
Distance Keeper
Most common mistake: Typing "Distance-Keeper" or "DistanceKeeper" or "The Distance Keeper" in the branch condition. The branch will never fire and the lead will fall to the fallback. Two words. One space. That's it.

2. Before You Build — Confirm the Form Is Working

Do not start building the workflow until you have confirmed the form is correctly saving the hidden result fields onto the contact record. If the form is not saving the result, the workflow will not work — even if the workflow is built perfectly.

The Pre-Build Checklist

Confirm the form exists. In GHL, click Sites in the left sidebar, then click Forms, then click Builder. Confirm the form named Dating ID Quiz Result Capture is listed.
Confirm the visible fields. Open the form. You should see three visible fields: First Name, Phone, and Email.
Confirm the hidden fields. The form should also have three hidden fields: Dating ID Result, Dating ID Source, and Dating ID Submitted Date.
Confirm the query mapping. Click each hidden field. The "Query Key" or "URL Parameter" setting should read result, source, and submitted_date — exactly in lowercase with the underscore.
Confirm the SMS consent language. The form must not show placeholder text like [BUSINESS NAME] or [USE_CASE_FROM_CAMPAIGN_DESCRIPTION]. If you see those, fix them before building anything else.
Run one live test submission. Go to the quiz page, take the quiz, submit the form. Then open the contact record in GHL and confirm the Dating ID Result field is filled with one of the five expected values.
STOP if this test fails: If a real test submission does not save the Dating ID Result onto the contact record, do not build the workflow yet. Message James. The hidden field query mapping needs to be fixed first.
How the website passes the result into the form (background info)

You don't need to do anything for this — it already works. This is here so you understand what's happening behind the scenes.

After the quiz calculates the result, the website dynamically rewrites the GHL form iframe URL to include the result and source as query parameters. Example:

https://api.leadconnectorhq.com/widget/form/oEaZHuklv7xBTqXYNY41?result=Optimist&source=dating-id-quiz

For "Distance Keeper," the space is encoded automatically as %20:

https://api.leadconnectorhq.com/widget/form/oEaZHuklv7xBTqXYNY41?result=Distance%20Keeper&source=dating-id-quiz

GHL reads those query parameters and writes them into the hidden form fields, which then save onto the contact record when the form is submitted.

3. Build the GHL Workflow — Step by Step

Follow these steps in order. Do not skip ahead. Each step shows you exactly what to click, what to name things, and how to know it worked.

1 Create the Workflow
  1. In GHL, click Automation in the left sidebar.
  2. Click Workflows.
  3. Click the blue + Create Workflow button in the top right.
  4. Select Start from Scratch.
  5. Name the workflow exactly: Dating ID Quiz Result Follow-Up
  6. Click Create.
You'll know it worked when: You see a blank workflow canvas with "Add New Workflow Trigger" at the top.
2 Add the Trigger
  1. Click Add New Workflow Trigger.
  2. From the trigger list, select Form Submitted.
  3. In the trigger settings panel, find the Filters section.
  4. Click + Add filters.
  5. Set the filter to: Form → is → Dating ID Quiz Result Capture.
  6. Click Save Trigger.
Do not skip the filter. Without the filter, this workflow will fire every time any form is submitted on the entire account. That would tag random leads with Dating ID tags. Always set the filter.
You'll know it worked when: The trigger card shows "Form Submitted" with "Form is Dating ID Quiz Result Capture" underneath.
3 Add the General Tags (4 tags, applied to every submission)

These four tags get applied to every quiz lead, no matter which result they got. Add them before the If/Else branch.

  1. Click the + button below the trigger.
  2. Select Add Contact Tag.
  3. In the tag field, type or select these four tags one at a time:
    • Dating ID Quiz Completed
    • Just Sayin Lead
    • Relationship Funnel
    • Quiz Lead
  4. Click Save Action.
If you get stuck: If a tag does not appear in the dropdown, type the exact tag name and press Enter. GHL will create it for you.
You'll know it worked when: The action card shows "Add Contact Tag" with all four tag names listed.
4 Optional — Create the Opportunity

Only do this step if the Just Sayin / Relationship Funnel pipeline already exists in GHL. If it does not exist, skip this step and move on to Step 5. Do not delay the build over this.

If the pipeline exists:

  1. Click the + button below the tag action.
  2. Select Create / Update Opportunity.
  3. Configure as follows:
    • Pipeline: Just Sayin / Relationship Funnel
    • Stage: Dating ID Quiz Completed
    • Opportunity Name: {{contact.first_name}} - Dating ID Quiz
    • Status: Open
  4. Click Save Action.
Not sure if the pipeline exists? Click Opportunities in the left sidebar. If you see "Just Sayin / Relationship Funnel," the pipeline exists. If not, skip this step and message James.
5 Add the If/Else Branch
  1. Click the + button below the last action.
  2. Select If/Else.
  3. For the first condition, set:
    • Filter type: Contact
    • Field: Dating ID Result
    • Operator: Equals
    • Value: Discerned
  4. Click + Add Branch four more times to add the remaining results: Optimist, Performer, Protector, Distance Keeper.
  5. For each new branch, repeat the same Field + Operator + Value setup using the exact result name.
  6. The final "Else" branch is the fallback — leave it as the default.
  7. Click Save Action.
Critical: Type the result names exactly. Capital first letter. No extra words. "Distance Keeper" is two words with one space.
You'll know it worked when: The If/Else action shows six branches: Discerned, Optimist, Performer, Protector, Distance Keeper, and Else.
6 Fill In Each Branch

For each of the five result branches, you will add three actions in this order:

  1. Add Contact Tag — the result-specific tag (for example, Dating ID - Optimist).
  2. Send SMS — the result-specific SMS (copy from Section 5 of this SOP).
  3. Send Email — the result-specific email (copy from Section 5 of this SOP).

The exact tags and messages for each branch are in Section 4 (Branches) and Section 5 (Messages) below.

If you get stuck: Build one branch fully (Discerned), test it once, and confirm it works. Then build the other four. Do not build all five before testing — fixing five broken branches is harder than fixing one.
7 Fill In the Fallback (Else) Branch

The Else branch only fires when none of the five result values match. This usually means something broke. Set it up like this:

  1. In the Else branch, add Add Contact Tag: Dating ID - Result Missing.
  2. Add Internal Notification (Send Email Internally) to James and yourself. Use the message in Section 4 below.
  3. Add Send Email to the lead with a fallback "retake the quiz" message.
You'll know it worked when: The Else branch has three actions: a tag, an internal notification, and a fallback email.
8 Save — But Do Not Publish Yet
  1. Click Save in the top right.
  2. Leave the workflow toggle in Draft mode for now.
  3. Do not flip it to Publish until you have completed every test in Section 6.
Why not publish yet? If the workflow has a bug, every real lead who hits it will get the wrong message or no message at all. Test first. Publish second.

4. The Five Branches — Exact Setup

Each branch checks the Dating ID Result custom field and matches one of the exact values below. Inside each branch, apply the result-specific tag and the result-specific messages.

Discerned
  • If Dating ID Result equals Discerned
  • Add tag: Dating ID - Discerned
  • Send Discerned SMS
  • Send Discerned email
Optimist
  • If Dating ID Result equals Optimist
  • Add tag: Dating ID - Optimist
  • Send Optimist SMS
  • Send Optimist email
Performer
  • If Dating ID Result equals Performer
  • Add tag: Dating ID - Performer
  • Send Performer SMS
  • Send Performer email
Protector
  • If Dating ID Result equals Protector
  • Add tag: Dating ID - Protector
  • Send Protector SMS
  • Send Protector email
Distance Keeper
  • If Dating ID Result equals Distance Keeper
  • Add tag: Dating ID - Distance Keeper
  • Send Distance Keeper SMS
  • Send Distance Keeper email

The Fallback (Else) Branch

If none of the five result values match, the Else branch fires. This usually means the hidden field didn't get the value, or someone typed the value wrong somewhere.

Add tag: Dating ID - Result Missing
Send internal notification to James and Chiara
Send fallback "retake the quiz" email to the lead

Internal Notification Message (copy/paste)

A Dating ID Quiz lead submitted the form, but the Dating ID Result was missing or did not match one of the five expected values.
Check the following:
1. The contact record — what is the Dating ID Result field value?
2. The form submission record — did the hidden field receive a value?
3. The hidden field query mapping in the form builder
4. The iframe URL on the quiz result screen
Expected values:
Discerned
Optimist
Performer
Protector
Distance Keeper
Most common mistake: The branch condition value must be exactly Distance Keeper — not Distance-Keeper, not DistanceKeeper, not The Distance Keeper. Two words. One space. Capital D, capital K.

5. The Messages — SMS and Email

The SMS is short and immediate. The email is longer and explains the result. Copy and paste each message into its branch. Do not rewrite them.

Option A: Universal Immediate SMS (if you want one SMS for all results)

This option only works if GHL correctly inserts the custom field value into the SMS body. Test it once before relying on it.

Hey {{contact.first_name}}, your Dating ID is {{contact.custom_fields.dating_id_result}}. I just sent your full breakdown by email too. Read it before your next "so what are we?" conversation. Just Sayin'.

Option B: Result-Specific SMS (recommended)

Use these five SMS messages, one per branch. Each one is tailored to the result.

Discerned SMS

Hey {{contact.first_name}}, your Dating ID is Discerned. You see patterns early, which is a gift — just don't let wisdom turn into emotional distance. Check your email for the full breakdown. Just Sayin'.

Optimist SMS

Hey {{contact.first_name}}, your Dating ID is Optimist. Your hope is beautiful — it just needs boundaries so it doesn't start doing unpaid emotional labor. Check your email for the full breakdown. Just Sayin'.

Performer SMS

Hey {{contact.first_name}}, your Dating ID is Performer. You know how to show up well — but love needs the real you, not just the polished version. Check your email for the full breakdown. Just Sayin'.

Protector SMS

Hey {{contact.first_name}}, your Dating ID is Protector. Your caution has wisdom in it — just make sure the wall isn't blocking the right person too. Check your email for the full breakdown. Just Sayin'.

Distance Keeper SMS

Hey {{contact.first_name}}, your Dating ID is Distance Keeper. Your peace matters — but sometimes the wall is doing too much. Check your email for the full breakdown. Just Sayin'.

Email Sequence — Timing and Content

Each branch should send an immediate email and then a follow-up sequence. The structure below is the same for all five results — only the result-specific language changes.

TimingMessageCall to Action
ImmediatelySend the full result explanation.Read the full breakdown. Visit Just Sayin' Interactive.
Wait 1 daySend "what your type tends to miss" reflection.Get the 5 Date Checklist.
Wait 2 daysSend "how your type shows up in conflict or uncertainty."Explore the Just Sayin' Interactive Guide.
Wait 4 daysSend book-centered relationship reflection.Buy the Just Sayin' book.

Approved CTA Links (use these in every email)

Dating ID Quiz: https://innershift360.com/dating-id-quiz/
Just Sayin' Interactive: https://innershift360.com/just-sayin-interactive
Just Sayin' College Edition: https://innershift360.com/just-sayin-college/
5 Date Checklist: https://innershift360.com/5-date-checklist
Just Sayin' Book on Amazon: https://a.co/d/09pdRhFe

6. Testing — Do Not Skip This

Before you flip the workflow from Draft to Publish, you must test all five branches. Each test should create or update a contact, save the right custom field, apply the right tags, and send the right messages.

Testing rule: Use a different test email or phone variation for each result. If you use the same email five times, GHL will merge them and you will not be able to tell which branch fired. Use chiara+discerned@example.com, chiara+optimist@example.com, etc.

Step-by-Step Testing Process

1 Open the First Test URL

In your browser, open the Discerned test URL:

https://innershift360.com/dating-id-quiz/?testResult=Discerned
2 Confirm the Result Screen Loads

The page should display the "Discerned" result and show the embedded GHL form underneath the result teaser.

3 Submit the Form With a Unique Email

Fill in the form using a test email like chiara+discerned@example.com and submit it.

4 Open the Contact in GHL and Verify

In GHL, click Contacts in the left sidebar, search for the test email, and open the contact record. Confirm every item below:

  • First name, phone, and email saved correctly
  • Dating ID Result field shows "Discerned"
  • Dating ID Source field shows "dating-id-quiz"
  • Tags applied: Dating ID Quiz Completed, Just Sayin Lead, Relationship Funnel, Quiz Lead, Dating ID - Discerned
  • SMS sent (check the Conversations tab)
  • Email sent (check the Conversations tab)
  • Fallback tag NOT applied — the contact should not have Dating ID - Result Missing
5 Repeat for the Other Four Results

Run the same process for Optimist, Performer, Protector, and Distance Keeper. Use a different email each time.

All Five Test URLs

ResultTest URLExpected TagExpected Custom Field
Discernedhttps://innershift360.com/dating-id-quiz/?testResult=DiscernedDating ID - DiscernedDating ID Result = Discerned
Optimisthttps://innershift360.com/dating-id-quiz/?testResult=OptimistDating ID - OptimistDating ID Result = Optimist
Performerhttps://innershift360.com/dating-id-quiz/?testResult=PerformerDating ID - PerformerDating ID Result = Performer
Protectorhttps://innershift360.com/dating-id-quiz/?testResult=ProtectorDating ID - ProtectorDating ID Result = Protector
Distance Keeperhttps://innershift360.com/dating-id-quiz/?testResult=Distance%20KeeperDating ID - Distance KeeperDating ID Result = Distance Keeper

Verification Checklist (for each test)

Result screen displays correctly: The page shows the expected Dating ID.
Embedded GHL form appears: The form loads under the result teaser.
Contact created or updated: First name, phone, email saved correctly.
Hidden fields saved: Dating ID Result, Dating ID Source, and Submitted Date.
General tags applied: Dating ID Quiz Completed, Just Sayin Lead, Relationship Funnel, Quiz Lead.
Result-specific tag applied: The correct Dating ID - [Result] tag.
Correct messages sent: The result-specific SMS and email fire.
Fallback did not fire: No "Dating ID - Result Missing" tag.
When to publish: Only after all five tests pass every item on the checklist. If even one branch fails one item, fix it and re-test before publishing.

7. Final Check Prompt — Have ChatGPT Audit Your Build

After you build and test the automation, paste the prompt below into ChatGPT along with screenshots of (a) the workflow canvas, (b) one test contact record, and (c) one form submission record. ChatGPT will tell you if anything is missing.

8. Reusable Template — For Future Quiz Automations

This Dating ID workflow becomes the model for every future InnerShift360 quiz. Same structure. Same naming patterns. Same testing process.

The Reusable Formula

1. Quiz calculates result on website.
2. Result screen displays a teaser.
3. Embedded GHL form appears under teaser.
4. Website passes result/source into form URL.
5. GHL form saves visible fields and hidden result fields.
6. Workflow triggers from the specific form submission.
7. Workflow applies general funnel tags.
8. Workflow branches by result custom field.
9. Each branch applies result-specific tag.
10. Each branch sends result-specific SMS/email.
11. Fallback branch catches missing or broken results.
12. Test every possible result before publishing.

Reusable Field Naming Standard

For every future quiz, use these naming patterns:

[Quiz Name] Result
[Quiz Name] Source
[Quiz Name] Submitted Date

Examples:

Life Alignment Result
Life Alignment Source
Life Alignment Submitted Date
Relationship Readiness Result
Relationship Readiness Source
Relationship Readiness Submitted Date
Family Protection Result
Family Protection Source
Family Protection Submitted Date

Reusable Tag Naming Standard

For every future quiz, use this tag structure:

[Quiz Name] Completed
[Brand/Funnel] Lead
[Quiz Name] - [Specific Result]
[Quiz Name] - Result Missing

Dating ID example:

Dating ID Quiz Completed
Just Sayin Lead
Relationship Funnel
Quiz Lead
Dating ID - Optimist
Dating ID - Result Missing

How to Add This SOP to SOP Central

Add a card or button inside /sop-central under the InnerShift360 / Just Sayin' automation section.

Title: Dating ID Quiz GHL Automation SOP
Description: Build and test the GHL workflow for the embedded Dating ID Quiz form.
Link: /sop-dating-id-quiz-automation/

Recommended category:

InnerShift360 Assessments → Relationship Funnel Automations

Final Completion Standard

This automation is complete only when all five Dating ID results have been tested individually and each one saves the correct custom field, applies the correct tags, and sends the correct SMS and email.

Done means tested. If only one result was tested, the workflow is not complete. Test all five: Discerned, Optimist, Performer, Protector, and Distance Keeper. Then — and only then — flip the workflow from Draft to Publish.
en_USEnglish
en_USEnglish
Scroll to Top