Flashtalking IDConnect, previously referred to as Connected Logs, provide clients with log-level data for activity across all of their campaigns. For example, our clients get a file containing all impressions, with one impression per row consisting of data such as the timestamp of the event, device information, geoinformation, and so on. Another file contains all clicks, with similar information, yet another file contains all spotlights.
IDConnect is perfect for large clients with a lot of data that they wish to ingest into their own/third party big data platforms for further analysis. They could use them to track individual user activity to measure different paths to conversion or perform a deeper analysis of device and geo information than what our standard reports provide.
While smaller extracts could, in theory, be opened in Excel for analysis, they will usually contain too much data. So ensure your client has access to data analysis resources before recommending this solution; the files are not designed with human-readability in mind and will require processing.
Setting up Flashtalking IDConnect
Raise a JIRA case in the Reporting project requesting they are enabled, containing the following:
- Confirmation that the client has read and understood the log file specification document.
- Confirmation that the cost applies to the rate card (or reason for waiving).
- Details of where they would like the files uploaded. This can be an FTP server (SFTP and SSH supported) or Amazon S3 bucket.
- If providing FTP details, please provide the hostname, username, password (option details can be a port number and default folder).
- If providing S3 Bucket details, you must give the Bucket Name, region, access key, and the secret key.
- In very special circumstances, if the client does not have their own FTP server or S3 bucket we can set them up some space, however, due to the size of the files this is not a recommended option, you should raise a JIRA issue requesting this. This space should be charged for (£500/$750 per month) and data will be removed after 30 days, as standard.
Note: Ensure that IDConnect is set up before campaigns begin. In most cases, it is not possible for us to provide historical log data, and in cases where we cannot go back very far.
There is a cost incurred. Discuss with your sales manager before requesting these are enabled.
IDConnect is delivered daily, as providing them any less frequently would result in files challenging to manage and process.
Limiting the Flashtalking IDConnect to only one Campaign
No, Flashtalking IDConnect is at the client-level and contains all of their data.
Log Extracts will come from IP addresses in one of these ranges; 18.104.22.168/27, 22.214.171.124/28, and 126.96.36.199/27
Due to the way log data is processed we cannot provide a partial sample of the data. However, we can provide a full day's worth of data at no charge, provided clients understand the specification and we have an FTP/S3 location to deliver it to.
Missing or Incorrect Custom Field (ft_custom/ft_section) Data
With custom fields, we simply pass back the data inserted into them at the time of the event. If the data in the field is blank, or incorrect, then it is almost certainly because the tags are not being populated correctly. Use Charles/Fiddler to check that tags are firing with actual data inserted, as third parties will often mistakenly insert macros or instructions (i.e. "[%INSERT_ID_HERE%]") instead of the actual data.
The following example specification needs to be sent to clients before taking the request any further, to ensure that the client can understand the specification and can integrate them into their platform.
To summarize, there are three main display files, containing data for all Impressions, Clicks, and Spots. In order to keep the size of these files down, we use IDs in these files to reference certain information. For example, instead of giving the name of a placement that is applicable to an individual impression, we'll give the ID.
The client will need to use the various match tables we also provide to determine which placement the ID represents. So the display file might tell them that there was an impression against placement id 123456, the placement match file will say to them that placement 123456 is named "Flashtalking Test Placement 600x300".