Uploaded image for project: 'AdMaxLocal'
  1. AdMaxLocal
  2. AML-3227

Subscriber provided Call Tracking Data is available for reporting in AML

          Details

          • Type: Task
          • Status: Closed
          • Priority: Major
          • Resolution: Fixed
          • Affects Version/s: None
          • Fix Version/s: Rushmore
          • Component/s: None
          • Labels:
            None

            Description

            Demo:
            Subscriber user provides merchant level call data (csv file) and it is available for AML Reporting

            As part of the onboarding process, the subscriber will adopt TSA format to send merchant level call tracking data, regardless of provider.

            We need to support call data from subscriber at Merchant level in the short term (and other lower levels, ideally keyword level, in the longer term).

            Format of data from the subscriber will require:
            Date, AML Merchant ID, Number of Calls.

            If Merchant ID is unrecognized, an exception is thrown for that row (rest of data should be imported) so that Tech Ops can address with Partner Support. The resolution would be that the data will have to be resubmitted with the current/correct Merchant ID

            If the subscriber only has the Static Call Tracking Number (from their call tracking provider), they will need to either provide a mapping table for TSA to import or TSA user or subscriber will have to update the csv file to include Merchant ID.

            process of importing data needs to be defined.

              Attachments

                Issue Links

                blocks

                Story - Created by JIRA Software - do not edit or delete. Issue type for a user story. AML-3289 TSA User can view generic merchant Level call data from Account level Data report

                • Major - Major loss of function.
                • Closed

                Story - Created by JIRA Software - do not edit or delete. Issue type for a user story. AML-3291 Subscriber user can track calls data for each merchant via Reseller UI

                • Major - Major loss of function.
                • Closed

                Story - Created by JIRA Software - do not edit or delete. Issue type for a user story. AML-3292 Merchant User can track Calls

                • Major - Major loss of function.
                • Closed

                Story - Created by JIRA Software - do not edit or delete. Issue type for a user story. AML-3298 Subscriber user can track calls data for each merchant via Merchant Performance Download report (Reporting API)

                • Major - Major loss of function.
                • Closed
                depends on

                Bug - A problem which impairs or prevents the functions of the product. AML-3322 Call Data Loader log output is not captured

                • Major - Major loss of function.
                • Closed

                Task - A task that needs to be done. AML-3302 Create merchant performance data table

                • Major - Major loss of function.
                • Closed

                Task - A task that needs to be done. AML-3303 Call data loader changes

                • Major - Major loss of function.
                • Closed

                Task - A task that needs to be done. AML-3321 Remove merchant_leads table

                • Major - Major loss of function.
                • Closed

                  Activity

                    People

                    • Assignee:
                      varshini.padmanabhan Varshini Padmanabhan (Inactive)
                      Reporter:
                      autumn Autumn (Inactive)
                    • Votes:
                      0 Vote for this issue
                      Watchers:
                      3 Start watching this issue

                      Dates

                      • Created:
                        Updated:
                        Resolved: