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

• ‘Connect’ sidebar item

  • This should show even if credential manager hasn’t been configured

  • If users navigate to ‘connect’ in sidebar without credential setup, the listing will be empty

• Campaign processr < visibility for publishers

  • For v1 this should be asingle toggle to apply to all publishers

  • V2 may have ‘per publisher selection’ if required

• Tab terminology

  • Changed from ‘Active Configurations’ and ‘Inactive Configurations' to ‘Pending Configurations’ and ‘Complete Configurations'

• Campaign selection (setup step)

  • Select ‘existing campaign’ should have advertiser filter first

  • Configration applying should be a 1 to 1 relationship, therefore the interface needs to change because you should only be able to select 1 campaign to apply the configuration to so no need for the ‘associated campaigns’ column on the listing. Users can then duplicate the campaign if they want to separate their lead delivery into multiple campaigns.

• Dashboard

  • New column to show if campaign is ‘connected’

• ‘Connect’ listing

  • Needs ‘domain’ column and ‘advertiser’ column

  • This means that users can add credentials for multiple enterprises and have campaigns from multiple sources come in (intentsify do this)

• ‘Job details’ for validation lists

  • Too many values to show if included on ‘jobs’ table, so dedicated table in ‘job details’ with pagniation will show values

• Step order changes

  • Mapping should be 2nd step as this dictates the mapping for jobs in step 3 because the form chosen from the linked enterprise would have all the mapping already setup, so this can be imported and then mapping is done without the need for any manual user input

• Audit of changes

  • Details will be on system level

• Campaign level connect integration

  • The ‘connect’ integration will be added, but without bits like API key and domain and this is done via credential manager

• Configuration pending updates

  • On jobs step, have column for ‘type of update’ then highlight the jobs that are new, updated, removed

• Form field mapping

  • Option to select ‘Unmapped’ if mapping is to be done later in the scenario where a different ‘mapping’ form is chosen and the field required for mapping is not available, so the field needs to be added after configuration is applied, therefore the ‘unmapped’ field allows the configure process to be completed and the field can be mapped later

• Configuration listing

  • Have 3 tabs instead of 2 tabs (previously ‘active’ and ‘inactive’)

    • ‘New configurations'

    • ‘Updated configurations' (this will need a column to show ‘linked campaigns’)

    • ‘Complete configurations' (this will need a column to show ‘linked campaigns’)

• Multiple ‘connect’ campaigns scenario

  • Intentsify use case have multiple campaigns sending to 1 linked enterprise campaign

    • If a campaign with a configuration applied is duplicated, will it also be ‘linked’ to the recieving leads enterprise and receive leads?

      • It will not be possible to apply configurations to multiple campaigns, but the ‘connect’ integration will still persist if duplicated, and leads can still be sent from multiple campaigns on sending leads enterprise to the receiving enterprise

• Potentially merge management screen with ‘dashboard’ somehow, maybe new tab?

  • Instead, have column on dashboard to show campaigns that have ‘connect’ integration on

Product

22/03/23

• Handing of updates

  • If a configuration change is made on recieving leads enterprise (i.e. a job is updated, job is added, job is removed) how do we track and send this across enterprises? Via job id?

    • Rokas: yes job id, map on the backend so we know which job corresponds to which job between enterprises

• Configure dialog > mapping step

  • Mapping fields only required if they choose their own form. If they choose the form as the form chosen on the linked enterprise then mapping not required

• Configure dialog > jobs step

  • Validation list values change from table of values to ‘download’ values button (private validation list will not allow downloading of values)

• Job names

  • Include actual jobs for examples

• Audit

  • How detailed will the ‘notes’ be here? E.g. this connect configuration was applied to this campaign. Or this connect configuration with these jobs with these settings was applied to this campaign?

    • It will be granular

    • Campaign level audit as well

• Campaign > processr

  • Have an indicator that it’s from ‘connect’

• Changing the linked campaign

  • What happens if a customer accidentally chooses the wrong campaign to apply it to? Because the campaign link is permanent, they can’t change the campaign? Have a way to ‘unlink’ the campaign and then the configuration can be applied again.

• Import all jobs from another campaign

  • Need to scope this? Will it import and replace any existing jobs? Can you select which jobs to import?

    • Will be discussed as a separate feature

Product

29/03/23

• Unlink dialog

  • Add some text to explain that once unlinked, the configuration will move to the ‘new configurations’ tab

• Dashboard

  • ‘Connect’ column to show which campaign has a linked job (previously it showed which campaigns had ‘connect’ integration job)

• Campaign > processr > connect job configuration

  • Add in domain and api key (prepopulated from credential manager)

Product

10/05/23

• Sidebar ‘connect’ item should always show, if no credentials are setup then table is empty.

• Recieving leads enterprise

  • Have an indicator (maybe on publisher assign) to say this campaign has no jobs or form

• Campaign status to be ‘connect’ unique, where if ‘not ready' (no form or jobs) then it cannot be setup

• Campaign details on configuration step, pre-populate (not advertiser and currency)

Product

05/07/23

Supplier

• Remove asterix from toggle

• Change wording for ‘select form used for job mapping’ to be specific about QA jobs

Demander

• Signed publisher contract is prerequisite for being allowed to apply config in connect management screen

  • Therefore, show a disabled ‘apply configuration button’ and add tooltip to explain that publisher contract needs to be signed

• Form convert to text fields

  • Multiselect fields (e.g. select/checkbox/radio) will be received as normal

  • Misc fields (e.g. html, hidden, whitepaper id, etc) will not be sent

Product & Dev

19/07/23

Supplier

• Changed terminology from ‘demander’ to ‘advertiser’ (yellow tooltips still say ‘demander’)

Demander

• Changed terminology from ‘supplier’ to ‘publisher’ (yellow tooltips still say ‘supplier’)

• ‘Apply configuration’ dialog

  • If ‘campaign to receive configuration’ is uncapped, then ‘leads required’ field will not be shown

  • ‘Leads required' and ‘per-action payout’ amount will no longer be prefilled (there are too many scenarios to show/hide/prefill/not prefill based on capped/uncapped/fix cost contracts, etc. for mvp)

  • ‘Currency’ will no longer be pre-filled as the naming convension between demander and supplier enterprises may not be set up consistenly

Product & Dev

26/07/23

Demander

• ‘Connect management’ page

  • Add filters to table columns to allow searching for campaigns, advertisers and enterprises