Installation Guide

1

Create a separate GA4 property for S2S

Keep your existing tracking intact — add a dedicated S2S property

💡 We create a new, separate GA4 property for server tracking. Your existing property and all historical data remain untouched.

📋 Create a new GA4 property

1

Go to Google Analytics and sign in.

2

Click the gear icon (Admin) in the bottom left.

3

Under Account, click Create Property.

4

Name it [Website name] — S2S (e.g. "TJDA - S2S").

5

Select your country, currency and timezone. Click Next → Create.

6

Under Data collection, choose Web → enter your domain → click Create stream.

7

Note the Measurement ID (G-XXXXXXXXXX) — you'll need it in step 4.

✓ New GA4 S2S property created

2

Duplicate GTM web tracking for the new property

Send web events to both your existing and new S2S property

⚠️ Do not modify your existing GA4 tag. Duplicate it so both properties receive web data.

📋 Duplicate your GA4 tag in GTM

1

Open Google Tag Manager and select your container.

2

Go to Tags and find your existing GA4 Configuration tag.

3

Click the three dots → Copy.

4

Open the copied tag and replace the Measurement ID with your new S2S property ID (G-XXXXXXXXXX).

5

Rename it to GA4 — [Website name] S2S so it's easy to recognise.

6

Also duplicate all GA4 Event tags (purchase, form events) and update them to use the new Configuration tag.

7

Click Submit to publish the changes.

💡 After publishing, check GA4 DebugView on the new property to confirm events are coming in from the browser.

✓ GTM tracking duplicated for S2S property

3

Install the S2S Conversions plugin

Free version available on WordPress.org

📋 Install via WordPress Admin

1

Go to WordPress Admin → Plugins → Add New.

2

Search for "S2S Conversions".

3

Click Install Now → Activate.

4

Go to Settings → S2S Conversions to configure the plugin.

✓ Plugin installed and activated

4

Get your GA4 API Secret

Required for the Measurement Protocol

📋 Create an API Secret in GA4

1

Open your new S2S GA4 property → Admin → Data Streams.

2

Click on your web stream.

3

Scroll down to Measurement Protocol API Secrets → click Create.

4

Give it a name (e.g. "S2S Plugin") and copy the secret value.

5

In WordPress: go to Settings → S2S Conversions → enter the Measurement ID and API Secret → Save.

✓ GA4 API Secret configured

5

Create GA4 Custom Definitions

Make server tracking parameters visible in your reports

📋 Add custom dimensions in GA4

1

Go to your S2S GA4 property → Admin → Data display → Custom definitions.

2

Click Create custom dimension and add the following:

Dimension name	Scope	Event parameter
csc_source	Event	csc_source
csc_consent	Event	csc_consent
form_name	Event	form_name
form_id	Event	form_id

3

Save each dimension. Note: dimensions are only applied to new data from this point onwards.

💡 Use csc_source = server in Looker Studio to filter and show only server tracking events — this is how you separate S2S from browser tracking.

✓ Custom definitions created

6

Create GA4 Explorations

Build custom reports for purchases and form submissions

📊 Purchase exploration

1

Go to Explore → Blank exploration.

2

Name it S2S Purchases.

3

Add Dimensions: Date, csc_source, csc_consent, Transaction ID.

4

Add Metrics: Transactions, Purchase revenue.

5

Add Filter: Event name = purchase.

📊 Form submission exploration

1

Create a new blank exploration named S2S Form Leads.

2

Add Dimensions: Date, form_name, form_id, csc_source, csc_consent.

3

Add Metrics: Event count.

4

Add Filter: Event name = generate_lead.

✓ GA4 Explorations ready

7

Looker Studio dashboard

Copy the template and connect your own data source

📊 Copy the S2S dashboard template

1

Open the S2S Conversions Looker Studio template →

2

Click the copy icon (top right) → Make a copy.

3

Under New Data Source, click Create data source → choose Google Analytics.

4

Select your S2S GA4 property → click Connect → Add to report.

5

Click Copy report — the dashboard is now in your own Looker Studio with your live data.

💡 The dashboard includes a csc_source = server filter so you only see server tracking events — no duplicate browser events.

✓ Looker Studio dashboard ready — GA4 setup complete! 🎉