Organise your multi-DSP Programmatic campaigns and optimization notes for fast reference and navigation.
Important: Downloading the package from GitHub means you are likely to be working on an alpha- or beta- pre-release package edition. For the most up-to-date edition of this package, install from the Google Chrome Store
- Download package to a local folder
- Visit
chrome://extensionsin your Chrome browser (or click Settings > Extensions) - Enable Developer Mode by toggling the switch in the top-right corner
- Click Load Unpacked and find the NeatDSP folder
Important: If you have downloaded the extension from the Chrome Web Store, your browser will automatically update extensions. The instructions below are just for local unpackaged installations
- Download package to a local folder
- Backup your 8881 NeatDSP data by clicking Settings > Export data
- Find your existing installation and back it up
- Replace the files in the existing installation folder with the contents of the package downloaded in Step 1
- (Optional) If your data is missing, navigate to Settigns > Import data and find the file saved from Step 2 to load your campaign data and notes
-
Create a new campaign object by visiting the middle tab, naming your campaign, and clicking the
+button- To select a campaign, either search using the drop-down on the top-right of the window, or click the name under All Campaigns
-
Add an object to your campaign object by visiting the page in your browser. If you are on a supported page (DBM, Yahoo! Brightroll, Amazon AAP are currently supported), you will see the "This Page" heading under the first tab. If there is an object that can be added to your campaign, you will see a
+symbol next to the name, Clicking this will add it to the campaign -
You can add notes and a priority level to each object. To do so, click the thermometer button to the right of the campaign. All notes are logged by timestamp and ordered by most recent
- Fork it
- Create your feature branch (
git checkout -b my-new-feature) - Write tests
- Make your changes
- Commit your changes
- Push to the branch (
git push origin my-new-feature) - Create new Pull Request
See the Release History for a list of all releases.
I use SemVer for versioning.
See full release notes in the changelog here for expanded details about changes for every release.
This project is licensed under the Apache-2.0 License - see the license file for details.