You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to set up a Zapier webhook to send data from Google Analytics to GoHighLevel custom fields, but I keep encountering issues with the field mappings and data types. Despite following the recommended steps, the webhook is not working as expected.
Steps to Reproduce
Create a New Zap:
In Zapier, create a new Zap.
Set Up Google Analytics Trigger:
Choose Google Analytics as the trigger app.
Set the trigger event to New Conversion Event.
Connect to the Google Analytics account and select the specific property and view.
Add Webhook by Zapier Action:
Choose Webhooks by Zapier as the action app.
Select Custom Request as the action event.
Configure Webhook:
Method: POST
URL: https://api.gohighlevel.com/v1/locations/1o3RsEW5fPCinW5vzt6z/customFields
Data Pass-Through: false
Unflatten: true
Basic Auth: Leave empty.
Headers:
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json
Data:
json
Copy code
{
"total_sessions": "{{values.total_sessions}}",
"new_users": "{{values.new_users}}",
"bounce_rate": "{{values.bounce_rate}}",
"average_session_duration": "{{values.average_session_duration}}",
"goal_completions": "{{values.goal_completions}}",
"page_views": "{{values.page_views}}",
"conversion_rate": "{{values.conversion_rate}}",
"traffic_source": "{{values.traffic_source}}",
"top_landing_pages": "{{values.top_landing_pages}}",
"exit_pages": "{{values.exit_pages}}"
}
Expected Behavior
The custom fields in GoHighLevel should be updated with the data from Google Analytics without any issues.
Actual Behavior
The fields do not update correctly, and I receive warning icons (exclamation points) in Zapier indicating issues with the field mappings.
Troubleshooting Steps Taken
Checked Field Mappings: Ensured that each placeholder is correctly mapped to the corresponding value from Google Analytics.
Verified Data Types: Confirmed that the data types match the expected types (e.g., numbers for numerical fields, strings for text fields).
Reviewed Payload Format: Validated the JSON payload format to ensure it is correct, with the appropriate fields and values.
Screenshots
Question
Could anyone provide insights into why the field mappings and data types are causing issues in this setup? Are there specific configurations or steps that I might be missing?
These are the suggested next steps that AI troubleshoot said
Suggested next steps:
Check the URL: Ensure that the URL you are using is correct and that the resource exists. For example, verify that https://api.gohighlevel.com/v1/locations/1o3RsEW5fPCinW5vzt6z/customFields is the correct endpoint.
Verify the Resource: Make sure that the resource you are trying to access (e.g., 1o3RsEW5fPCinW5vzt6z) exists in the app.
Bug Description
I am trying to set up a Zapier webhook to send data from Google Analytics to GoHighLevel custom fields, but I keep encountering issues with the field mappings and data types. Despite following the recommended steps, the webhook is not working as expected.
Steps to Reproduce
Create a New Zap:
In Zapier, create a new Zap.
Set Up Google Analytics Trigger:
Choose Google Analytics as the trigger app.
Set the trigger event to New Conversion Event.
Connect to the Google Analytics account and select the specific property and view.
Add Webhook by Zapier Action:
Choose Webhooks by Zapier as the action app.
Select Custom Request as the action event.
Configure Webhook:
Method: POST
URL: https://api.gohighlevel.com/v1/locations/1o3RsEW5fPCinW5vzt6z/customFields
Data Pass-Through: false
Unflatten: true
Basic Auth: Leave empty.
Headers:
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json
Data:
json
Copy code
{
"total_sessions": "{{values.total_sessions}}",
"new_users": "{{values.new_users}}",
"bounce_rate": "{{values.bounce_rate}}",
"average_session_duration": "{{values.average_session_duration}}",
"goal_completions": "{{values.goal_completions}}",
"page_views": "{{values.page_views}}",
"conversion_rate": "{{values.conversion_rate}}",
"traffic_source": "{{values.traffic_source}}",
"top_landing_pages": "{{values.top_landing_pages}}",
"exit_pages": "{{values.exit_pages}}"
}
Expected Behavior
The custom fields in GoHighLevel should be updated with the data from Google Analytics without any issues.
Actual Behavior
The fields do not update correctly, and I receive warning icons (exclamation points) in Zapier indicating issues with the field mappings.
Troubleshooting Steps Taken
Checked Field Mappings: Ensured that each placeholder is correctly mapped to the corresponding value from Google Analytics.
Verified Data Types: Confirmed that the data types match the expected types (e.g., numbers for numerical fields, strings for text fields).
Reviewed Payload Format: Validated the JSON payload format to ensure it is correct, with the appropriate fields and values.
Screenshots
Additional Information
Zapier platform version: [version]
GoHighLevel API endpoint: https://api.gohighlevel.com/v1/locations/{location_id}/customFields
Google Analytics trigger setup details: [details]
Repository
zapier/zapier-platform
Question
Could anyone provide insights into why the field mappings and data types are causing issues in this setup? Are there specific configurations or steps that I might be missing?
Reproduction Steps
{
"total_sessions": "{{values.total_sessions}}",
"new_users": "{{values.new_users}}",
"bounce_rate": "{{values.bounce_rate}}",
"average_session_duration": "{{values.average_session_duration}}",
"goal_completions": "{{values.goal_completions}}",
"page_views": "{{values.page_views}}",
"conversion_rate": "{{values.conversion_rate}}",
"traffic_source": "{{values.traffic_source}}",
"top_landing_pages": "{{values.top_landing_pages}}",
"exit_pages": "{{values.exit_pages}}"
}
Zapier Platform version
newest version
Node.js version
Newest version
Your Operating System
PC
npm/yarn version
No response
App ID
No response
More Details
No response
The text was updated successfully, but these errors were encountered: