digitalpoint
Well-known member
Dumb question I know, but have you had someone register since you enabled it?
register_complete
template, so if you aren't using that template because of some other addon or process you have, or have overwritten it (or simply don't show it to the user for whatever reason), the sign_up event won't show.You navigated to that page starting at the Admin index? The error really looks like you navigated to that reporting page starting from a public page (if you clicked the chart icon in the moderator bar, that's the wrong thing to do... because that's reporting ONLY for that page, not the site). The icon in the moderator bar is not simply a shortcut to something in the admin area because I thought people care so much about reporting they can't use the normal admin navigation (it's reporting specifically for the page you clicked it from).I am doing this from the Admin home page.
Right, that's not what you want to do if you want to see reports for your site. The ONLY use of that icon is if you are trying to get analytics report including just data for the page you clicked it from (and nothing else).I must have driven to it from the home page top right analytics icon.
I'm not worried about page titles. its the page content, media files and attachments that are sensitive. We don't want our content appearing in Google searches.If you had goals setup for your old UA, I’d just continue with those. Conversions are going to be unique to your business/site and whatever you consider important. There’s some info here for migrating from goals to conversions, but you are effectively asking others what you should consider important in your website (only you can answer that):
[UA→GA4] About this conversion migration guide - Analytics Help
Replicate your UA goals and conversions in Google Analytics 4This guide has three main sections: "GA4 conversion essentials", "Map goals to GA4 conversions", and "Conversion use cases by marketinsupport.google.com
If you are wanting to break down GA reporting by user groups, use it. Otherwise you don’t need it.
If you don’t want Google to store your sites analytics data (which will include certain things like page titles), you don’t want to use this addon. There’s no way around that as it’s a Google product, so they store the underlying data for you.
Ya maybe wait a day or two after the property was created and see. Not sure why other events would be different but maybe it is somehow.![]()
Google Analytics changed what dimensions are compatible and no longer allow full page URL to be used in conjunction with most other dimensions/metrics. Because of that, we are switching to something that works reasonably well as far as compatibility in reporting (page path).
Error: Call to a member function getBody() on null src/addons/DigitalPoint/Analytics/Repository/JavaScript.php:53
Stack-Trace
#0 src/addons/DigitalPoint/Analytics/Cron/CleanUp.php(24): DigitalPoint\Analytics\Repository\JavaScript->getFile('gtm', true)
#1 src/XF/Job/Cron.php(37): DigitalPoint\Analytics\Cron\CleanUp::runHourlyCleanUp(Object(XF\Entity\CronEntry))
#2 src/XF/Job/Manager.php(260): XF\Job\Cron->run(8)
#3 src/XF/Job/Manager.php(202): XF\Job\Manager->runJobInternal(Array, 8)
#4 src/XF/Job/Manager.php(86): XF\Job\Manager->runJobEntry(Array, 8)
#5 job.php(43): XF\Job\Manager->runQueue(false, 8)
#6 {main}
ErrorException: cURL error 28: Connection timeout after 3000 ms (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) src/XF/Error.php:77
Stack-Trace
#0 src/XF.php(219): XF\Error->logError('cURL error 28: ...', false)
#1 src/addons/DigitalPoint/Analytics/Repository/JavaScript.php(50): XF::logError('cURL error 28: ...')
#2 src/addons/DigitalPoint/Analytics/Cron/CleanUp.php(24): DigitalPoint\Analytics\Repository\JavaScript->getFile('gtm', true)
#3 src/XF/Job/Cron.php(37): DigitalPoint\Analytics\Cron\CleanUp::runHourlyCleanUp(Object(XF\Entity\CronEntry))
#4 src/XF/Job/Manager.php(260): XF\Job\Cron->run(8)
#5 src/XF/Job/Manager.php(202): XF\Job\Manager->runJobInternal(Array, 8)
#6 src/XF/Job/Manager.php(86): XF\Job\Manager->runJobEntry(Array, 8)
#7 job.php(43): XF\Job\Manager->runQueue(false, 8)
#8 {main}
We use essential cookies to make this site work, and optional cookies to enhance your experience.