Import Events data using Google Sheet
If you have data that is not available in your CRM but that you would like to see in Dreamdata's platform we have enabled a solution to upload data using Google Sheets (following this template). This could be data from any field marketing activities (e.g. webinars, conferences, in-person events and trade shows).
Dreamdata will connect the uploaded events (such as webinars, conferences, etc.) to stages and the reports available in the App.
Follow these steps to setup:
- Download the template or make a copy of it to keep the Google Sheets format
- Insert your events data (see explanation below) and add view access to the sheet for google-sheets@dreamdata.io
- Paste the sharing link of the Google Sheet into the empty field found under Sources -> Import Events data and click Upload Link. You can add as many sheets as you need
Where do I see the result of adding events data?
The shared events data will be visible in the Event report (found under the Engagement section) and any new data added to the sheet will be automatically included. The events are then used throughout the App as filters in all the relevant reports.
The sheet is read three times a day, and new rows show in reports after the data modelling run that follows the next read. See Data Modelling Schedule for how the timing works.
How do I use the template?
The event data is imported using the schema as shown in the template.
Please do not: add new tabs to the sheet (data has to be in the first tab), add extra columns, rename or rearrange any of the columns as the data will not be uploaded correctly.
One sheet can have maximum 250 000 rows, if you have more relevant data please split it in multiple sheets
Required columns:
event: the name of the event (any names are accepted and there is no limit for how many names can be added)
email: email address of someone that attended the event (attendee)
timestamp UTC: the date and time when the event happened (required format: YYYY-MM-DD hh:mm:ss)
Optional columns:
event_id: can be used for debugging
user_id: if data comes from a platform that provides this information
company_id: if data comes from a platform that provides this information
website: website of the company where the event attendee is employed
company_name: company where the event attendee is employed
url: the url of the page where the event happened. UTM parameters and LinkedIn ad ids in the url are read, see "How do I connect imported events to LinkedIn ads?" below
referrer: from where the above url was accessed
source: some examples are webinar and conference. This should match a sources shown in the Dreamdata platform (case sensitive)
channel: can be the same as the source or a group of sources. This should match a channels shown in the Dreamdata platform (case sensitive)
region: region of the country of the event attendee
country: country of the event attendee
city: city of the event attendee
browser: used for online events only, where the url was accessed
browser_version: version of above browser
os: used for online events only, operating system through which the browser was accessed
os_version: version of above operating system
device: used for online events only, one of the following choices: desktop, mobile, tablet and tv
How do I connect imported events to LinkedIn ads?
If you know which LinkedIn Ad or Ad Set an imported event came from, add its id to the url column. The Dreamdata Platform reads the url the same way it reads a tracked page view, and shows the event under the matching LinkedIn Campaign, Ad Set and Ad. The names come from your connected LinkedIn Ads account, so the imported events line up with your LinkedIn spend in ROI reports, down to Ad Set level.
This needs the LinkedIn Ads integration to be connected, and the ids must belong to a connected LinkedIn ad account.
Fill in these columns
Column | Value |
source |
|
channel |
|
url | Built from the LinkedIn id, see the next table |
campaign | Optional, for example your own UTM campaign tag. It is kept as the event's UTM campaign. |
Build the url from the LinkedIn id
You know | What to enter | What gets filled in |
The Ad |
| Campaign, Ad Set and Ad |
The Ad Set |
| Campaign and Ad Set |
Only the Campaign | Leave the url empty and enter the exact LinkedIn Campaign name in the campaign column | Campaign |
You can find the ids in LinkedIn Campaign Manager, for example in the Ad ID and Ad Set ID columns of an export.
Good to know
- Use a full url that starts with https://, with no spaces and no # part.
- The source and campaign columns take priority over
utm_sourceandutm_campaignin the url. Other UTM parameters, such asutm_medium, are read from the url. - Values read from the url are stored in lowercase.
- If two Ad Sets in your LinkedIn account have exactly the same name, only one of them can be matched by its Ad Set id. Use the Ad id for events from those Ad Sets, or give the Ad Sets unique names.
- Campaign, Ad Set and Ad names are shown as they are in LinkedIn today. Earlier names or an earlier campaign structure can't be imported.
- Do any lookups or helper columns in a separate sheet: only the first tab is imported, and extra columns aren't allowed.
- The ROI cost import sheet has no Ad Set or Ad columns. LinkedIn spend at Ad Set level comes from the LinkedIn Ads integration.
- If the events are LinkedIn Lead Gen Form leads, check that they aren't already in the Dreamdata Platform before you import them, so they aren't counted twice.
For clicks on your LinkedIn ads, set up the tracking template in Tracking LinkedIn Ads, so the same ids are captured automatically.
