Support

Please click on one of the support topics below to read more.

DFP – Proof

DFP – Proof PackageMaker is an online service that allows you to upload one or more PDF-files, and receive zip-packages back that are ready for upload to DFP – Proof

The service will extract images for each page in the PDF and save those for 24 hours. You will need to upload the package to DFP – Proof within that time to ensure that the upload is successful.

Open PackageMaker Upload PDF files Uploaded PDF files

We currently offer licensed extension panels for Adobe CC that will allow you to integrate with DFP – Proof, and handle the proofing process from within your favourite applications. Please follow the intstructions below to install and configure them.

1. You will need to store the thumbnails of images on a webserver that is publicly reachable from the Internet. This is needed since DFP – Proof fetches these assets when importing the zip-package. As we do not currently support authentication we strongly suggest that you store your images in hard to guess location, and switch off directory browsing on your webserver.

As the extension panels are built for Adobe Creative Cloud you will be able to use the file storage provided in your Adobe CC license. The setup described below shows how you use this service to store your files, but you may use any other webserver of choice. If you intend to use your own webserver you may now skip to step 6.

Make sure that you have logged in to your Adobe CC account, and that all files are up to date.

Adobe CC panel

2. Create a folder with the name "DFP_PROOF" within your Adobe Creative Cloud folder, it may be placed anywhere as long as it is within the Adobe CC folder. This will be the folder where thumbnails and other necessary assets for DFP – Proof are stored.

3. Right click the DFP_PROOF folder and select "Collaborate"

Adobe CC collaborate link

4. When the Adobe CC web browser opens, click the share icon for the DFP_PROOF folder

Adobe CC collaborate link

5. Get the sharable link, and save it for later. It will be used to configure the extension panels

Adobe CC get sharable link

6. Download one of the Adobe CC extension installers available from third party developers. We suggest using zxpinstaller

7. Start the installer and drag the DFP – Proof extension file in .zxp format directly on to the installer window. The extension will be installed to all Adobe CC applications by doing this.

8. Start Adobe Bridge, InDesign, or Illustrator, as these applications support all our extension panels, and open the installed panel from the Window menu.

Adobe CC extension menu

9. Select Preferences from the extension panels top right corner. The configuration file will open in your systems default text application. Make sure that this is an application that supports editing of text files.

We suggest using BBEdit on OS X, or Notepad++ on Windows.

Adobe CC extension menu

10. Configure the extension panel. For normal use only the parameters below need to be edited. If you provide the optional user name and password, you will not need to fill these in each time you open the extension panel.

  • dfpproof_domain_user: (optional) your e-mail address used to log in to DFP – Proof
  • dfpproof_domain_user: (optional) your password used to log in to DFP – Proof
  • thumbnailBaseUrl: the URL to the DFP_PROOF folder on your webserver. See step 5
  • packageFolderPath: the file path to the DFP_PROOF folder. Please note that the path is in forward slash format also on Windows systems, as in "/Users/your username/Creative Cloud Files/DFP_PROOF/"
  • thumbnailBasePath: the file path to a subfolder named dfpProof that will be created in the DFP_PROOF folder. Please note that the path is in forward slash format also on Windows systems, as in "/Users/your username/Creative Cloud Files/DFP_PROOF/dfpProof/"
  • zipBasePath: the file path to where you would like to store zip packages for upload to DFP – Proof. This will normally be identical to thumbnailBasePath.

11. If you are installing more than one extension panel, please repeat steps 9 and 10 for each panel. At the time of writing all our panels have an identical set of parameters, so they all share the same config file. This could change at any time, so please review settings for each new extension panel.