There are three possible reasons why no campaigns or ad groups were generated.
1. Empty table
If the campaign defining table of a template is empty, no campaigns will be generated. If on the other hand a support table is empty, it is possible that no ad groups are being generated, while the campaigns are generated.
2. Google Account not set
The second possible reason is that the Google AdWords account is not set in the campaign defining table. If the column “account_google” already exists, please select a Google Account or a dummy account (e.g. “Main Account”). If the column is not present in the campaign defining table, please go into the table settings, click “Add new column set” and select “google account”. Afterwards fill the new column “account_google”. If you have a big table, use a dynamic rule for filling in the account.
3. Custom structure contains mistakes
Some users don’t use the default naming convention from deltamethod. Instead they define a custom one under “Settings” > “Define Structure” in templates. However, this procedure is prone to cause problems. We highly recommend to use the default structure. Common mistakes of custom structures are wrong spaces in functions. Furthermore, often if-conditions are defined too strictly with the consequence that nothing gets generated.
Relations can prevent certain combinations of table entries from being created. If you are missing a certain combination of table entries (e.g. an ad group) these are the steps to investigate:
1. Do you use manual relations?
Please figure out whether you are combining tables with manual relations or not. Such relations are not required. If tables are put into the same template without using relations, all entries from all tables are being combined.
2. Do you use a mapping table?
In the template, which appears to be missing content, please check under “Settings” > “Relations” if an item is selected under “Create items only if referenced in [Select a table]“. This selection is for mapping tables. (A mapping table is a table, which contains a list of all allowed combinations. This can be a product table, a search term mapping table or a manually created mapping table.) If a table is selected there, please go to that table and check if relations to the other tables of the template exist. Furthermore, make sure that the missing combination exists in this mapping table.
3. Do you have a product table assigned to the template?
Please note that you can achieve the same effect as under 2. by assigning a table to a template. If you have a mapping table assigned to a template (e.g. your product table), please check if the missing combination exists in that table. If not, please add it and export the template again.
4. Additional hint for the usage of feeds
In case you are using a feed to update a mapping table (e.g. a feed is regularly updating your product table), please be aware of the fact that there might be contents missing in your feed. It often happens that the feed is updated but the new version does not contain a certain entry. If the feed setting “Remove missing rows from Campaign Suite table” is selected (in the table details page under “Feed” > “Feed Settings”) an update of the feed, which suddenly no longer contain a certain entry, will remove this entry from the Campaign Suite. Therefore, if you use a feed, please always check if the missing entry is possibly missing in your feed.
In a Campaign Suite table, a certain name value is always chained to its id. For example, imagine the name entry “shoe” has id 12. If you delete this row from the table and create a new row and give it the name “shoe” again, this entry will get the id 12 again – no matter how many other items are in that table. The reason for this procedure is that the campaign or ad group name for the “shoe” ad group would otherwise change. Campaign and ad group names from the Campaign Suite are created based on table prefixes and table ids.
Certain table IDs will be missing in a table if their row was deleted. Imagine to have a table with 12 entries. If the last name entry is “shoe” and the row is deleted, then another row is created with the name “boots”, this row will have the id 13. The id 12 will no longer exist in the table, because it is chained to “shoe”, which was removed.
Table prefixes cannot be changed, because they are used in campaign and ad group names. Changing them would change the campaign and ad group names of all contents, which are based on the changed tables. This in turn would cause subsequent problems. For example, you would lose the AdWords history of all those campaigns and ad groups.
This is our most general error message. It usually refers to any kind of system problem. If you encounter this message during an export or in any other place of the application you would do us a great favor informing us about it. Please write an email at firstname.lastname@example.org and describe the situation.
Due to browser-specific issues the fields, which can handle variables, behave differently in different browsers. If you have problems in Firefox or Chrome you might want to try the other browser instead.
If you have written a long combination of variables, functions and static text and then you notice that you must delete something in the middle, follow this workaround: First navigate to the end of the item, which you want to remove. If the cursor is there, enter a white space. Now navigate before the white space and delete as many items as necessary. In the end remove the white space. This way entries in the middle of a string can be deleted without the problem of deleting too much or even everything.
Templates, which require review, cannot be exported. Therefore, they are not available to be selected in the export page. Please click “Open template”, navigate to the tab, which contains the error(s) and solve them. After that, go back to the export page and export the template.
The Campaign Suite expects certain conditions in order to be able to accept tables. Please make sure that the following conditions are met in your table:
1. No duplicate columns or rows
If the same column name exists multiple times, this will prevent the table from being imported – even if only one occurrence of the column shall be imported. Furthermore, the column that is mapped to the name column of the table is not allowed to contain duplicate entries. The Campaign Suite removes white spaces from the beginning and end of words. Therefore, if you have two similar words, which only differ by a space, these will be considered as duplicates. For example, “brand” and “brand ” will be considered as duplicates by the Campaign Suite.
2. Correct structure of the file
A text file (like a CSV or TXT), which contains a table, uses a separator. This can be a comma or semicolon or certain other characters. Please make sure that each row contains the same number of separators. If the first row has e.g. 7 fields and therefore 6 separators (commas/semicolons) between the fields, the second row must also have 6 separators. This counts for the whole file.
The Campaign Suite supports the following encodings: UTF-8, UTF-16, UTF-16LE, UTF-16BE, Win 1251, ISO-Latin-1. If your file has a different encoding, please use a text editor (e.g. Notepad++ on Windows, gedit on Linux) to change the encoding.
If the table is still not importable, please let us know at email@example.com. We will try to find the reason.
If you encounter that some contents are categorically missing in an export file, this might be related to the selection of export sets. The Campaign Suite offers to export only subsets of the generated contents. A feature called “export sets” allows users to select on the first step of the export flow, which contents to export. It is possible to deselect “Keywords” or “Text Ads” or other contents.
In case you exported a file and afterwards you noticed that it does not contain a certain group of contents, please have a look at “Recent downloads” and at the “Export sets” selection. Both are available from the first page of the export flow. The list of recent downloads mentions, which sets were exported. Thereby you will understand if a wrong selection of export sets was the reason.
Active or paused text ads are missing
It might happen that some ad groups are missing expected text ads in the export (and in the template preview). This happens if one of the text rows in the ad template had more characters than allowed. In order to make sure that this never happens, please always use static text in the last fallback of an ad template. And this static text should, of course, not have more characters than allowed. The number of allowed characters can be varied under general settings from the user drop down menu.
Deleted text ads are missing
The full download does not export deleted text ads. The reason is that for some templates, where the ads were changed multiple times, the export files would otherwise contain huge numbers of deleted ads (e.g. 50 of them). Therefore, if you need to export deleted text ads, please make sure to use the button “Download Changes” on the third step of the export flow.
Always check the settings!
Under general settings (user drop down menu > Settings) there is an option to edit the desired text ad length. Please make sure that you didn’t mistakenly select a text ad length, which is too short. This would cause many of your ad texts to drop to the next fallback or even hinder them from being generated, if even the last (static) fallback is considered to be too long.
In many cases, when a CSV file is directly imported into Microsoft Excel, some cells display zero values or some false values. This happens for the Broad match modifier type (+), since the symbol (+) for Broad match is misinterpreted as some formula by Excel which it is unable to evaluate.
But this undesirable behaviour can be easily avoided by using following simple steps while importing a CSV file:
- Open a blank Excel workbook
- Click on “Data” on the toolbars tab and select “From Text”
- Select the CSV file you want to import
- In the “Text Import Wizard – Step 3 of 3″, Select all the required columns
- Select button “Text” instead of “General” for the Column data format and click on Finish
Now, the Excel does not treat the content as formula anymore and true value is displayed inside the cell.
Such a behaviour is only visible in Excel and not Google AdWords Editor. Inside Editor you can easily import the CSV without worrying about the false representation of content
The Campaign Suite offers to export negatives. These keywords are part of export files, where they appear in the “Keyword” column. However, the column “Match Type”, which is also in those files, defines them as “Negative Phrase” or “Negative Exact” (depending on the type of negative). When the Campaign Suite export file is being opened in the AdWords Editor, make sure to map the column “Match Type”. If this column is not mapped, the AdWords Editor interprets all contents of the “Keyword” column as positive keywords. Even negatives will be seen as positive keywords, if this match type column is not used during the import of the Campaign Suite export file to the AdWords Editor.
The Special URL can help to organize special URLs, but still some problems can occur. To learn more about how to deal with them, click here and read the advanced hints at the end of the article.
When importing to the AdWords Editor, a warning may be triggered stating that the location is unresolved although a Location ID is shown correctly. To make sure that location settings are set up properly, click on the gear symbol and select “Settings”. If the “Target countries” are correct , the location can be resolved by posting the changes to AdWords. We recommend to set the campaigns for which the locations were unresolved to “paused” before posting the changes and check if the Location ID has been correctly recognized by AdWords.
Let’s assume you intend to set a relation from the “category” column in your product feed to the “name” column in the category table. In many cases it happens that the brand, category, … tables contain other names for equal items compared to their names in the product feed. For example, the category table might have the name value “Shoes” while the feed calls the same items just “shoe”. In such a case, it’s not possible to set up a relation between the feed column and the name column of the category table, because the Campaign Suite will not understand that these are the same items. The best solution is to create a second column in the category table, which is called “feed_names”. There write “shoe” into the “Shoes” row. Afterwards, relate the “feed_names” column with the category column inside the feed.