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

Reporting/Analytics user can easily run reports for clients on different realms on the same stack

    Details

    • Type: Story
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: Mercury
    • Component/s: None
    • Labels:
      None
    • Story Points:
      13
    • Sprint:
      Sprint 14, Sprint 15, Sprint 16
    • Epic Link:

      Description

      Today, Reporting/Analytics team cannot easily separate out merchant performance data by realm if multiple realms are on the same stack.
      .
      We need to provide a way, either via scripts and/or multi-tenant structure so that the AML reporting/analytics team can pull merchant data more easily.

      This can be provided by creating the internal daily reports by realm (instead of by stack). The expectation is that the internal AML user will either (both are requirements):
      specify specific realm and report name or
      expect all reports can be generated for all realms within the stack.

      the spec for the internal daily reports are found on http://kbase.ri.thesearchagency.com/index.php/Image:Internal_TSA_Reporting_for_AdMax_Local.docx
      Please keep in mind AML-3718 which will generate two more reports for Bing (Keyword Leads and Ad Leads) and i will create this "different realm" requirement on a separate ticket for those.

      Please exclude the following reports from this request:
      Search Engine Campaign Data
      BA/Loc CustomizationReport (since it already has a reseller value in the report)

        Attachments

          Issue Links

            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:

                  Time Tracking

                  Estimated:
                  Original Estimate - 2 weeks
                  2w
                  Remaining:
                  Remaining Estimate - 2 weeks
                  2w
                  Logged:
                  Time Spent - Not Specified
                  Not Specified