Push campaign configuration from one enterprise to another.

00/00/2021
to
00/00/2021
(0 Days)

Metric name

• Metric Value

HYPOTHESES

• Lorum ipsum

REASONING

• Lorum ipsum

EMBRACE

REJECT

TO DISCUSS

Product

08/03/23

DONE

REJECTED

NEED MORE INFO

TO DISCUSS

• GENERAL

  • General terminology confusion

    • Sender is sending campaign or sending leads?

    • Reciever is recieving campaign or receiving leads?

  • Mocks

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

  • 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.

    • Or could be called something completely different such as ‘Sync’ or ‘Link’

• SENDING 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?

    • 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?

  • Global vs campaign level

    • I know we already discussed campaign level but just want to discuss to cover all the bases). Global level would allow a higher level management view of which campaigns have ‘convertr connect’ on and running. This would be feasible if ‘credential manager’ sorts out the ‘linking’ between enterprises, therefore users don’t need to go into campaign > processr to do any convertr connect setup.

    • If we do campaign level, on dashboard we may need a new column to show which campaigns have ‘convertr connect’ running?

    • If no global level, campaign level would live under ‘admin’ dropdown?

  • 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?

SENDING ENTERPRISE MANAGEMENT SCREEN STEPS

• Listing

  • Only need listing if on global level

• 1

  • Global form selection

  • Field mapping

  • Lead locking stuff here (needed for v1?)

• 2

  • Select which QA processr jobs to include

• 3

  • Review (similar to campaign creation ‘review’ step which will show all campaign settings)

  • Once all complete, the ‘Save/Sync’ button will push campaign to ‘receiving’ enterprise

RECIEVING ENTERPRISE MANAGEMENT SCREEN STEPS

• Listing

  • Each line item is a configuration

  • Publisher notes dialog

• 1

  • Advertiser selection

  • Category selection

  • Publisher 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?)

  • Field mapping

• 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

• Processr jobs will be read-only

TO DO

00/00/2021
to
00/00/2021
(0 Days)

Metric name

• Metric Value

HYPOTHESES

• Lorum ipsum

REASONING

• Lorum ipsum