Posts Tagged ‘Integration’

NEW – Data Actions Divided by Tabs in Integration Jobs February 28, 2010 No Comments

There are different types of data actions that constitute a job:
Import Actions
Keyword actions
Ads actions
Settings
Export actions
Now the actions are divided by tabs, therefore when creating a job it is easier to understand the architecture and the function of each action.

New – Eliminate Duplicate Values in Integration Jobs No Comments

By using the Data Criteria >> Filter job action, now users can eliminate duplicate values from the feed.

Using URL at Keyword Level in Integration Jobs No Comments

Using the URL at keyword level can be now predefined when creating an integration job. By checking the box in the “Remove Keyword Level URL” option in Default Values >> Criteria, the user can decide at which level to include the URL provided by the feed.

Include Users Runs on Job Runs Reports No Comments

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.

New in adCore™ – Automatic Jobs/Schedule Tasks Names February 25, 2010 No Comments

adCore™ now provides a coherent name to new jobs and schedule tasks. Please note that the name can be changed if desired by the client.

Additional Parameters When Creating Ads in Integration Jobs on adCore™ January 18, 2010 Comments Off

When creating ads for integration campaigns, adCore™ gives the option to include the url in the ad as a parameter [url]. This is a special benefit for content campaigns because allows to create ads with deep links. Likewise the maximum price can be included by using the parameter [lp]. These parameters allow to create ads [...]

New on adCore™ – Adding Job Actions in the Desired Place Comments Off

When creating a job in adCore™ the order of the job actions takes an important role. For this, when a new job action is added it will appear where the cursor is, assuming that the cursor is where logically the job action is expected to be added.