YouTube Link: youtu.be/ugklLFbij-A.
IFTTA is a game changer in rule-based marketing. With our tool you can run marketing campaigns based on real world events. We already support the following data sources:
- Weather (based on OpenWeatherMaps API). The Weather conditions that you already can use: temperature, wind speed, cloudiness, rain, snow, thunderstorm.
- Pollen and Air Quality (Ambee API).
On the marketing activation side we support the following platforms:
- DV360 (via the DV360 API)
- Google Ads (via the Ads API)
Keywords: Weather Based Marketing, External Signal Based Marketing, Pollen Based Marketing, AirQuality Based Marketing, Rule-based Marketing.
- Advertisers want to show their ads as targeted as possible to reach the right audience at the right time
- Managing ad campaigns in response to real-time events like weather, pollen data or air quality can be challenging to impossible (just imagine, manually switching hundreds of ad groups on a daily basis... it is really time consuming and an error-prone)
Our tool will do this for you automatically!
Basically all advertisers can benefit from this solution and especially those that clearly see a correlation between the real world factors (e.g. weather) and sales (or other marketing KPIs).
Some examples to ignite the imagination (based on our experience):
- Hot beverages can be advertised during the colder weather and cold beverages during the warm weather
- An ice cream company can show ads when it’s hot
- Insurance companies can show ads when there’s a storm or a flood
- A hardware store might show ads for snow shovels when it snowed
- Healthcare companies can advertise based on the pollen index and/or the air quality
- Ads will reach their audience at the right time under the right circumstances
- Advertisers can automate their campaign management in response to real-time events
- Personalized ads and WOW effect on the end user side (since the user will see the right ad at the right time)
Basic Google Cloud knowledge and a Google Cloud project with enabled billing are required.
With the following simple steps you can install IFTTA on your Google Cloud project. The installation below is partly automated, this means that you will need to do some manual steps at the beginning and at the end the installation script (the big blue button below) will do the rest.
-
Create an OAuth Consent Screen
-
Make it of type "External"
-
Add all users you want to have access to the app
-
Create an OAuth Client ID
-
Set Application type to "Web application"
-
Set the name to "if-this-then-ad"
-
Take note of the Client ID and Client Secret presented to you
-
Click the big blue button to deploy:
-
Choose the Google Cloud Project where you want to deploy the app
-
Select the region where you want to deploy
-
Enter your Client ID and Client Secret when prompted
-
Ignore any other prompts, which will get auto-populated
-
Make sure you add the Authorized JavaScript origin as well as the Authorized redirect URI presented to you at the end of the script to your OAuth Client
We love to hear your feedback! Please create an issue directly on GitHub. Please be specific describing your question/bug/feature.
- Clone this repository
- Complete the step-by-step guide above
- Create a new GCP Service Account (or add another key for it, if it already exists)
- Download the
.json
credentials - Rename
server/.env.sample
toserver/.env
- Add all missing values to
server/.env
- Go to
server/
- To set up and start the server, run:
npm run build-local
npm run dev
- Go to
client/
- To set up and start the client, run:
sudo npm i -g @angular/cli
npm i
ng serve --ssl
- The application is running at https://localhost:4200
To do all the checks before the commit automatically please add the git/pre-commit to your .git/hooks/
directory. The easiest way would be to create a soft link: cd .git/hooks/; ln -sf ../../git/pre-commit
.
To run all checks manually you can execute the following commands from the project root:
- For server:
cd server; npm run pre-commit
. - For client:
cd client; npm run pre-commit
.
You can start contributing by sending pull requests right now! Also you can give us a star on our GitHub page ;-)
This usually originates from not having the Authorized redirect URI set properly.
Here's how to fix it:
- Go to Cloud Credentials
- Select the right project
- Click on the if-this-then-ad OAuth 2.0 Client ID
- Add the redirect_uri presented to you in the error message to Authorized redirect URIs