February 28, 2010 in Reporting, Settings, Update
Tagging can help to create groups of campaigns and see different statistics of these groups. In addition to this, adCore™ now added the option to include several tags in the campaigns. This can be applied to every campaign just by separating the tags by commas.
February 28, 2010 in Integration, Maximization, Reporting
The job reports show the job runs that take place in adCore™. Now the report can be filter by jobs that run automatically and by those run by the user. Just check the box next to the job status and decide the run jobs that you want to see.
January 18, 2010 in Reporting
The activity report on the adCore™ reporting section is one of the most useful tools for our clients. For this, we included a column for the number of the campaigns in each channel.
August 19, 2009 in Reporting, Settings
By opening campaigns under the new generic “Display” channel, adCore™ can monitor none SEM/SCE campaigns. For this, the advertiser needs to copy and add the adCore™ generated Google Analytics tag from the “Analytics Tag” link on the campaign settings form and add them to the external campaign URL.
August 19, 2009 in Reporting, Settings
Each client will now have an assigned “Manager” (an agency level user). The system will allow filtering clients’ activities, jobs, reports and forms by the client manager.
August 19, 2009 in Reporting, Settings
With the tag filter, the client is able to see reports divided by grouping or to filter information. As well there is the option to choose the distribution network desired (search, content or both), making analytics reporting even more specific for the client’s needs.
August 5, 2009 in Reporting
The benchmark report in adCore™ has now the option to choose a desired gap for comparing two different dates whereas negative numbers refer to past time intervals and positive to future time intervals. The dates range can be 7, 14 or 30 days.
If a positive gap (+1 or +2) is chosen, choose to send the report and the system will store the benchmark report request and will automatically send it on the 1st day after the benchmark period ended.
This is an example:
