(New UI) Validate landing pages in bulksheet files
Accounts with destination URLs only
You can validate the landing pages in all destination URLs in a single-account bulksheet file. You can specify any phrases and URLs that indicate an invalid page and optionally report landing page redirects as errors. Search, Social, & Commerce checks for your specified conditions and for missing landing pages (which result in HTTP 404, or “Not Found” errors).
When it finds errors, Search, Social, & Commerce creates a bulksheet error file that includes all rows in the original bulksheet and error messages for all rows with invalid landing pages. The errors are noted in the EF Errors column. The file name convention is <bulksheet name>__lpv_errors.<extension used for the bulksheet>.
You can later download the file, correct the errors and upload the corrected file, and then post the corrected file to the ad network account.
- This feature doesn’t validate values in the Base URL/Final URL column.
- You can post bulksheet files while they are being validated, or even if errors are found.
-
In the main menu, click Setup > Bulksheets.
-
Select the check box next to each file to validate.
note NOTE You can validate only single-account EF bulksheets that aren’t currently in progress. If you select a multi-account bulksheet or a bulksheet that’s currently being processed, those files are excluded. -
In the action bar, click Validate URLs.
-
In the dialog, enter information in the fields, and then click Apply:
Enter case-sensitive text or phrases that indicate an invalid page (one per line): Text in the body of a landing page that indicates the page is invalid. To specify multiple values, enter them on separate lines.
Enter invalid landing pages (one per line): The URLs of pages that are invalid as landing pages. To specify multiple values, enter them on separate lines.
User Agent: How the landing page validation agent is identified to the web server on which the landing page resides. The default is
default, which attributes views by the agent to an anonymous Mozilla Firefox user. If the web server blocks requests from anonymous Mozilla Firefox users, then enter the name of a different agent. For example, for Googlebot, enterGooglebot/2.1;+http://www.google.com/bot.html.Report redirects as errors: When a landing page redirects to another page (for example, if the landing page is missing and the site displays a substitute page), the EF Errors column in the landing page error file indicates the URL to which the landing page is redirected.
When the task begins, a new row is added to the Bulksheets view. When email notifications for bulksheets are enabled within Notification Center, then an email notification with a link to the file is sent when the file is created. Depending on the amount of data compiled, the email notification may take several minutes or more. You can download the file to edit it and then reupload it for posting, or you can post the file as-is.
- Large files take longer to validate.
- Bulksheet files for multiple campaigns can contain up to 500,000 data rows. If you generate data for multiple campaigns and the combined data consists of more than 500,000 rows, then the data is split by campaign into two or more files named
<bulksheet name>_1.tsv,<bulksheet name>_2.tsv, and so on.