Push campaign configuration from one enterprise to another.

https://www.figma.com/proto/yOJOddCozfN5PtKzGyobYQ/CONNECT---Listing?node-id=24-2&scaling=scale-down-width&page-id=0%3A1&starting-point-node-id=24%3A2

Product

0817/03/23

• GENERAL

  • General terminology confusion

    • Sending and recieving can be both ways depending on context, e.g. if talking about campaign or leads

  • Mocks

    • Need to include all things in this v1 of mocks, i.e. lead locking, cross-platform comms?

      • V1 is campaign creation and notifications. Notfications’ would be an indicator of sorts to say you need to change this/this has been updated, etc.

  • New name

    • When we release new version, it will of course go into a BETA phase and therefore the ‘old’ convertr connect will still be available. Therefore, new version needs a different name, but Instead of calling it ‘Convertr Connect V2’ or something to that effect, maybe we just call it just ‘Connect’? I think having the company name in the job name is inconsistent, we don’t call the processr the ‘Convertr Processr’ and no other jobs have ‘Convertr’ in the name.

      • Call it ‘Connect’ everywhere

• SENDING CONFIGURATION ENTERPRISE

  • Syncing to recieving enterprise/credential manager

    • The ‘syncing' of campaigns (API key, domain, publisher, campaign id) could be done via credential manager as a one time setup and therefore ‘convertr connect’ integration job and specific convertr connect qa jobs no longer required?

      • No processr job required for convertr connect integrations

      • Sending configuration enterprise would select QA jobs to include, recieving enterprise would create those jobs but as a ‘convertr connect’ version job (e.g. val list values will be shown but as read only and will be updated as the ‘source’ platform makes their updates, similar to how current campaign information works)

    • BUT, how will apikey/campaignid/pubid retrieval work? Because the campaign is not created in the receiving enterprise yet as still needs to be ‘accepted’ and then the campaign ID and pub id can be retrieved?

      • Credential manager would just have api key and domain

      • Magic will happen once the campaign has been accepted to sort the campaign/publisher linking

  • Global vs campaign level

    • Global level

  • Management screen

    • Do we still need a ‘sync’ button or will this action happen when we ‘push’ the campaign/configuration to the receiving enterprise?

• RECIEVING ENTERPRISE

  • Duplicating ‘connected’ campaigns

    • For v1 will we cater for 1 to many relationship of sending configuration to recieving enterprise, i.e. are we allowing dupliating of ‘connected’ campaigns as some customers have expressed a need for this?

  • Overwrite or append stuff

    • An update is made to a job on sending enterprise, the receiver accepts it and it overwrites the old configuration? Or does it append extra stuff?

    • Do we need an audit page to see previous configurations that have been ‘pushed’?

SENDING ENTERPRISE

• Processr

  • Will have new column on jobs to ‘expose to publisher’

RECIEVING ENTERPRISE MANAGEMENT SCREEN STEPS

• Listing

  • Each line item is a configuration

  • Publisher notes dialog

• 1

  • Advertiser selection

  • Category selection

  • Which other stuff from campaign creation setup? (e.g. start end date, financial stuff, campaign manager, basically all the ‘required’ things?)

  • Toggle to update lead/create new lead (needed for v1?)

• 3

  • Field mapping

    • Could ‘clone’ form from ‘source’ enterprise and this would update if the ‘source’ enterprise updates their form

    • Or can choose own form and then fields would have to be manually updated

• 2

  • Select which QA processr jobs to include

• 3

  • Review (similar to campaign creation ‘review’ step)

  • Once all complete, the ‘Save’ button will create the campaign

RECIEVING ENTERPRISE CONNECTED CAMPAIGNS