How-To: Set Up Alli RSA 2.0

his article provides info on how to onboard to the new Alli RSAs workflow for both Google and Bing RSAs

1. Copy this sheet: https://docs.google.com/spreadsheets/d/1qTfL2-qPnuc5gP5TD8fdeISmkFPScmhSvFFQlT2RbKQ/edit?usp=sharing . Do not edit the original, choose File-> Make a copy and edit the copy.

2. While making a copy, be sure to check the “Share with the same people” checkbox. Also ensure to share with your client’s Google Service Account. You can find this in your client’s settings page on Alli.

3. Once you’ve made a copy of the sheet, you can start editing the sheet with your inclusion/exclusion and RSA details. For more details refer to matching logic documentation.

4. Go to HQ page, select the engine (Bing vs. Google) and enter your account ID.

   Finding Your Account ID:

   For Bing:
   • Login to Microsoft Ads
   • Go to Settings > Account Settings
   • Use the "Account ID" field (numeric only, e.g., 150314605)
   • DO NOT use "Account number" (e.g., F119KK38) - this won't work

   Alternative method:
   • Copy the URL when viewing your account
   • Find the parameter AID="150314605" in the URL
   • Use that numeric value

   For Google:
   • Login to Google Ads
   • The Account ID appears below your account name (format: XXX-XXX-XXXX)
   • Use the full ID including hyphens, or remove them
   • Example: 123-456-7890 or 1234567890 (both work)

5. Copy the Google Sheet ID, which is the long string of characters between /d/ and /edit in the sheet URL. Example: https://docs.google.com/spreadsheets/d/1AbCdEfGhIjKlMnOpQrStUvWxYz/edit

   → Sheet ID = 1AbCdEfGhIjKlMnOpQrStUvWxYz

   You’ll need this ID later when setting up the workflow.

Step 2: Setting up the Workflow Task

1. Go to http://marketplace.alliplatform.com and choose your client from the top left.

2. Search for RSA 2.0 and click Install.

3. These are the variables that you would need to fill:

   1. notification_emails: Email Id of the person/people to whom the notification emails should be sent. This would notify the successful or failed execution of the task.

   2. hq_sheet_name: Leave this blank if you’re using Google Sheets. If you’re using smartsheets, enter the name of your HQ sheet here.

   3. hq_sheet_id: The sheet ID of your Google sheet that you created in the first step.

   4. hq_tab_name: The tab name in your Google Sheet that contains account and mapping details. this will most likely be “HQ”

   5. slack_channel_for_bulk_upload_file: The slack channel to which your RSA bulk upload sheet should be sent to.

   6. slack_channel_for_errors: The slack channel to which your workflow task errors should be sent to.

   7. people_to_at: The people who you want to be tagged when an RSA sheet is sent to slack.

   8. communication_type: Whether you want to receive the bulk sheet through slack, or email, or both.

   9. email_recipients: If your communication type is email or both, fill in the email IDs of the people to whom the bulk sheet should be sent.

   10. output_type: output_type: You can choose between “Submit Live” which would submit the RSAs to Google with a “PAUSED” ad status, or “Download bulk upload sheet” which would generate a bulk upload sheet and send on slack. You can later manually QA the bulk upload sheet and upload it to Google. Please note: the bulk uploads option will send a notification to slack with the processed CSV, users can choose to do it this way and upload this CSV to bing/google ads manually with the added ability to QA before submission, or choose submit live, which will still send that CSV to designated Slack Channel, and then proceed to submit the RSAs to the platform automatically. Alli can handle that from start to finish

   11. Login customer id: Google/Bing login customer id (Manager level MCC ID)

   12. Match All Identifier : Match All Identifier

       The value which can be used to in either the Account Inclusions or Camp / Adgrp Inclusions columns to signify you would like to match to all possible options. defaults to All.

   13. Ad Status : he status for newly created RSAs. Choose:
       • "ENABLED" - New RSAs will be active and can serve immediately
       • "PAUSED" - New RSAs will be created but paused (recommended for first run to QA before going live)

       
       

4. Please be aware, the workflow will only run 1 engine at a time. Do not attempt to run too frequently. it is always advised to wait a few minutes to run the next attempt.