A step-by-step guide on how to send data to collect.
Our Collect destination is a managed Big Query Data Lake that you get full access to when activating it. An activated Collect destination is necessary to use our default dashboard and you can also run SQL over the raw elbwalker data.



Activate the destination

After you created the collect destination you can activate it by using the toggle.
Please make sure that you've activated the destination and implemented the script to your site to collect data successfully. Please also note that it can take up to 5 minutes until data will be collected due to caching mechanisms.

Configure the destination

You can customize your destination by clicking edit in the dropdown menu.
All events you added to the event screen will be send to the destination by default. You can choose which events you don't want to collect by deselecting it in the configuration modal.
All events that you are measuring at the point of time you activated the destination will be send by default. If you add events later on, you will have to manually add them to the list if you also want to send it to this destination.

Cross Domain Tracking

By default the domain is encrypted in our user hash in a way that you can't recognize the same user across different domains. If cross domain tracking is mandatory for your business case, e.g. when using different subdomains, all you need to do is to enable cross domain tracking in the configuration modal. This will remove the domain from the hash function.
Please make sure that you checked the requirements of your users' consent with your legal department for cross domain tracking.

Exclusion Parameters

To exclude specific parameters from the data collection you can use the input fields in the configuration modal. This is especially useful if you want to proactively avoid that personal identifiable information (PII), e.g. email addresses, are being collected through the URL inadvertently etc. Parameter values will be replaces with xxx. This way you can test if an exclusion worked.
Input in collect configuration modal
Output in databaseRaw Data Access
We help you to protect your users privacy at all times 🔒

Raw Data Access

We give you full access to your raw event data. All you need to know is a little SQL to do your own custom analyzes.
Currently we have to manually add your email address to the dataset so please send us an email to [email protected] with the subject Raw data access first, if you have not already done so. The elbdatalake is based on Big Query. A Google Cloud account will be required to access your raw data.
Once you click raw data access in the dropdown menu of your collect destination you will open
Your data set consist of three tables Sessions, Events & Entities should appear in the menu on the left under elbdatalake-1.
Pay attention to the following when setting up
  1. 1.
    An active project must be created or selected.
2. Make sure that European Union or Automatic (= EU) is selected under processing location in the query settings. Otherwise no queries will be possible. If everything is configured correctly, you can now start analyzing! 🚀
You can alsouse the raw data to build you own custom reports in e.g. Google Data Studio.
We don't recommend activating multiple collect destinations for one project.
Got questions? Contact us, we can help 🤓
Last modified 25d ago