TABLE OF CONTENTS
FAQ: Understanding the Difference Between Call Reporting and Agent Reporting
Q: What is the difference between Call Reporting and Agent Reporting?
Q: How do the filters differ between Call Reporting and Agent Reporting?
Q: Why might there be a mismatch between Call Reporting and Agent Reporting data?
Q: How can I ensure accurate reporting when comparing data from Call Reporting and Agent Reporting?
Q: Why is the Call count different between Google Ads Platform and our Call Reporting section?
FAQ: Passing Parameter-Value Pairs with GA4 Events via Workflows
A: Call Reporting and Agent Reporting are two distinct features in our system that serve different purposes. Call Reporting focuses on tracking calls based on the assigned phone numbers, while Agent Reporting focuses on tracking calls based on individual agents/staff members.
A: In Call Reporting, the filter is applied based on the assigned phone number, which may have a given name such as "Max." On the other hand, in Agent Reporting, the filter is applied based on individual agents/staff members.
A: The mismatch between Call Reporting and Agent Reporting data can occur due to the nature of how calls are tracked. In Agent Reporting, the call count includes all contacts assigned to Max, as well as calls received or made by Max. However, in Call Reporting, the calls made to contacts assigned to Max may have been handled by someone else, leading to differences in statistics.
A: To ensure accurate reporting, it's essential to understand the differences between the two reporting methods and the factors that may contribute to discrepancies. When comparing data from Call Reporting and Agent Reporting, consider the specific filters applied and the criteria used for tracking calls in each system. Additionally, verify that the configurations align with your intended reporting objectives to minimize any potential discrepancies.
A: The Call count shown in Google Ads Platform is not directly linked to our Call Reporting section. We do not display the Call count from the Google Ads Platform in our reporting. To track calls through Google Ads, users can set up a Number pool and add the number pool script on the website where they want to track calls. If users have set up a Number pool but are not seeing accurate call tracking, they may need to ensure that the number pool script is correctly implemented on their website. For detailed instructions on setting up call tracking in our platform, refer to this article: How to Set Up Call Tracking Number Pool
A: The data mismatch for different users can be attributed to various factors, one of which may be the difference in timezones between the users.
A: Differences in timezones can impact data recording and reporting, especially when dealing with time-sensitive events such as call logs or activity timestamps. If users are located in different timezones, their actions may be recorded based on their local time, leading to discrepancies in data when compared across different users.
A: The Revenue displayed on Facebook Ad Reporting originates from Opportunity data, not directly from the Facebook Ads platform. This distinction arises because the client needs to configure two workflows to integrate Facebook conversion data with our platform. The same applies to Sales count and Leads count. For a step-by-step guide on setting up the conversion API for leads events, which consequently populates Sales count and revenue values in Facebook Ad Reporting, please refer to this article: Facebook Conversion Leads Walkthrough
A: The revenue displayed on the location dashboard represents the sum of the Monetary value of WON opportunities, rather than the actual payment received. This revenue metric is tied to opportunities and not directly linked with the integrated payment system.
A: The Lead count in Google Ads is attributed to contacts whose first attribution is "Paid Search" and originated from Google ads with utm_source=adwords and gclid indicating the Google click ID. This occurs when the client's setup is incorrect, such as missing tracking templates or precautionary scripts. Additionally, discrepancies may arise if the actual campaign name differs from the contact's campaign name or if the campaign name exceeds 250 characters.
A: The Sales count on Google Ad reporting reflects the number of Google Ad Lead opportunities marked as WON. If the opportunity status was changed to anything other than WON or if the Leads count is 0, the Sales count will be 0 as well. Sales count dynamically updates based on changes to opportunity statuses and is a subset of Leads count.
A: Changes in opportunity statuses, particularly if an opportunity was marked as WON on multiple occasions within the same date range, can cause fluctuations in the Sales count. The count reflects the date of the last status change to WON, and opportunities may be excluded if their status changes.
A: Google Conversion may fail if the tracking template or precautionary script is not properly added, leading to incomplete data. Discrepancies between the data sent back to Google Ads API and the actual data may also result in conversion failures. Make sure to add the tracking script and precautionary script. Refer to this document for the steps
A: The Sales count on Facebook Ad reporting reflects the number of Facebook Lead opportunities marked as WON. This count is directly linked to the Leads count on the Facebook Ad Reporting. The Sales count will only appear if the Lead Event workflow is correctly set up. Ensure that the FB Lead Event workflow is configured properly, as outlined in this helpful article: Facebook Conversion Leads Walkthrough. If the opportunity status is changed from WON to another status, or if the Leads count is 0, the Sales count will be 0.
A: Changes in opportunity statuses, particularly if an opportunity was marked as WON on multiple occasions within the same date range, can cause fluctuations in the Sales count. The count reflects the date of the last status change to WON, and opportunities may be excluded if their status changes.
A: The Facebook Ad Reporting displays Leads and Sales based on the Campaign Name, Ad Group Name, and Ad Name. To avoid contacts repeating in multiple campaigns, ensure that these names are unique. Repeated contacts may occur if the Campaign Name, Ad Group Name, or Ad Name are identical. Ensure that these names are distinct to prevent contacts from appearing multiple times.
A: For emails sent through SMTP integration, we track opened, clicked, replied, and bounce events.
A: SMTP integration doesn't provide visibility into all email events, limiting us to specific actions like opens, clicks, replies, and bounces.
A: To compensate for missing events, we preprocess the data when other events occur. For example, if an email is opened, we assume it was delivered as well and update the delivered count accordingly.
A: Due to our preprocessing approach, where opened emails are assumed to be delivered, the opened and delivered counts may appear identical. This is because we update the delivered count upon an email being opened.
A: Currently, we do not have a direct method to pass Parameter Name and Parameter Value in a GA4 action through workflows.
A: Event Value refers to a numerical value assigned to an event to signify its significance or monetary worth. This value allows for quantifying specific interactions, aiding in the analysis of their impact on business objectives.
Check Permissions: Ensure that the required permissions are enabled for the respective user profile. For example, permissions for contacts should be enabled to view contact-related widgets on the dashboard.
Assigned User Settings: If the "ONLY ASSIGNED USER" option is enabled in settings, users will only see data and metrics linked or assigned to them. Ensure that users have the appropriate assignments configured to access the desired data.
Verify Date Range: Make sure the date range is correctly set on the dashboard. For example, if you are validating data shown on the contacts page and dashboard, ensure that both pages have the same date range added for correct and synchronized data display. Double-checking the date range alignment can help ensure accurate data representation across widgets.
