Manage integrations with your community site, including Google Tag Manager and Google Analytics.
You can access the integrations settings by clicking the Integrations button under the Community Site module in your Tightknit app home.Within the Integrations modal you can configure Google Tag Manager, a free tool that allows you to manage and deploy marketing tags (snippets of code or tracking pixels) on your website without having to modify the code.
You can connect your Google Tag Manager to the Tightknit community site. All you need is your GTM ID. Below is a detailed guide on how to connect Tightknit to Google Tag Manager and Google Analytics, including how you can track custom Tightknit events.
Click the ⚙ Admin Button in the bottom left corner
Click the +Create button and select Property
Copy the Measurement ID (G-XXXXXXXXXX)
Now, we’ll return back to Google Tag Manager to add the Google Analytics Property to our container. This will forward all activity on all page views to GA.
Create a new GTM Tag:
In the Workspace view, navigate to Tags on the left hand navigation
Click the New button
Click the Tag Configuration section and select Google Analytics > Google Tag
Paste the Measurement ID from above (G-XXXXXXXXXX) into the Tag ID field
Click the Triggering section, select Trigger Configuration, and then ‘Initialization - All Pages’
Click Save
Submit the GTM changes and publish
3
[Optional] Track Tightknit Events
In order to track the custom events from Tightknit, you must configure tags and variables.
Navigate to Triggers in the sidebar and click the New button
Select the Trigger Configuration section
elect “Custom Event” for the trigger type
Give an Event name such as “Tightknit CTA button click”
Fire the trigger on “Some Custom Events”
Reference the Tightknit Event in the table below. Set the trigger condition to equal the Event. For example: Event equals tk-cta-button-click
Click Save
Create a Variable to capture the event’s variables
Navigate to Variables in the sidebar and click the New button under the User-Defined Variables section
Select the Variable Configuration section
For the Variable Type, select “Data Layer Variable”
For the Data Layer Variable Name, enter the name exactly as the variable appears in the Events table data layer variables. For example, use location for the location variable.
Leave the remaining fields with their default values
Click Save
You can reuse the same Variable object across multiple events if the Data Layer variable name is exactly the same. For example, location is the same across several events.
Create a Tag for the event
Navigate to Tags in the sidebar and click the New button
Select the Tag Configuration section
For Tag Type, select “Google Analytics: GA4 Event”
For Tag ID, enter the GA measurement ID from the earlier step (G-XXXXXXXXXX)
Under Event Parameters, add a new parameter. For the Event Parameter, use the name of the data layer variable, e.g. location. For the Value, click the lego variable button and select the Variable created from the previous step.
Select the Triggering section
Under Firing Triggers, add a new item and select the name of the Custom Event trigger you created in the first step
Click Save
Submit the GTM changes and publish
From this point onwards, the events and variables will be pushed to Google Analytics. However, you must still configure a custom dimension for the variables to appear in reporting.
Click the ⚙ Admin Button in the bottom left corner
Navigate to Property Settings > Data display > Custom definitions, in the sidebar
Click Create custom dimension
Enter a descriptive name for the Dimension name. Select “Event” for the Scope. Enter the exact data layer variable name for the Event Parameter, e.g. location.
Click Save
To verify your setup:
Trigger a real event on your Tightknit site, e.g. click the Call to Action button.
Go to Reports > Engagement > Events.
Ensure the time window (top-right) is appropriate, e.g. last 24 hours.
You should see some recent events, including the Tightknit events. If you click on the event item, you should see an event-specific dashboard and the ability to filter by the data layer variables we configured earlier!