trackLocation() calls | Community
Skip to main content
jeff_bloomer
Community Advisor and Adobe Champion
jeff_bloomerCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
July 26, 2018
Solved

trackLocation() calls

  • July 26, 2018
  • 8 replies
  • 6121 views

Good Morning, Gigazelle​

I am looking to get some clarification related to the trackLocation call.

I know that it should be set to fire every time the user launches the app, but I want to understand something:

  • The instructions mention that trackLocation works the same as trackAction.  As a result, if we start sending trackLocation on a number of our calls, do we have the option to combine the data fired in our trackAction into trackLocation, or will we now be sending two calls and increasing our cost?

Jeff Bloomer

Senior Analyst, Digital Analytics Implementation

The Kroger Co. | Digital Site Experienc

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by Jennifer_Andrews

    Hi Jeff,

    Yes, you can indeed send additional contextData same as a trackAction call.  It would again depend on your requirement, it's likely not necessary to send trackLocations for each Action, the location, I would think would not move significantly from Launch until sending subsequent actions.

    Jen

    8 replies

    Gigazelle
    Adobe Employee
    GigazelleAdobe Employee
    Adobe Employee
    August 9, 2018

    trackAction and trackLocation both send image requests, so you'd be increasing costs by sending both simultaneously. However, you can send additional data in a trackLocation call, as indicated here: Geo-Location and Points of Interest

    Mobile Services is unfortunately not my forte, so I'm afraid I won't be able to go into much more detail than that

    jeff_bloomer
    Community Advisor and Adobe Champion
    jeff_bloomerCommunity Advisor and Adobe ChampionAuthor
    Community Advisor and Adobe Champion
    August 9, 2018

    Thanks.  Anyone on your side who would have additional insights?

    jantzen_b
    Adobe Employee
    jantzen_bAdobe Employee
    Adobe Employee
    August 9, 2018

    Jen Andrews​ - Do you have any inputs here?

      jeff_bloomer
      Community Advisor and Adobe Champion
      jeff_bloomerCommunity Advisor and Adobe ChampionAuthor
      Community Advisor and Adobe Champion
      August 9, 2018

      I guess the point I'm getting to is, should I start considering scenarios where I might replace the trackAction call to fire as trackLocation and fire the same context variables I'm currently firing in addition to the location data?  The goal here is to see an aggregate of users who are using the app within 100 meters of one of our locations or not.  Thanks again!

      Jennifer_Andrews
      Adobe Employee
      Jennifer_AndrewsAdobe Employee
      Adobe Employee
      August 28, 2018

      Hi Jeff,

      A trackLocation request sends in the equivalent of a trackAction call.  Generally, you would send trackLocation when the app starts, and then as you as often as you need based on the requirements of your app.

      Jen 

        jeff_bloomer
        Community Advisor and Adobe Champion
        jeff_bloomerCommunity Advisor and Adobe ChampionAuthor
        Community Advisor and Adobe Champion
        August 28, 2018

        Hi Jen!

        I totally understand what you're saying.  What I'm wanting to know is if it's possible to replace a trackAction call with trackLocation and still fire all of the relevant variables I had in trackAction so I can preserve the amount of calls being fired.

        For example, say I would normally capture adding an item to my cart using trackAction.  Is it possible to fire trackLocation instead and still pass all of the values I would have passed in the trackLocation call; or, do I still have to fire both calls separately?

        Jennifer_Andrews
        Adobe Employee
        Jennifer_AndrewsAdobe EmployeeAccepted solution
        Adobe Employee
        August 28, 2018

        Hi Jeff,

        Yes, you can indeed send additional contextData same as a trackAction call.  It would again depend on your requirement, it's likely not necessary to send trackLocations for each Action, the location, I would think would not move significantly from Launch until sending subsequent actions.

        Jen

          jeff_bloomer
          Community Advisor and Adobe Champion
          jeff_bloomerCommunity Advisor and Adobe ChampionAuthor
          Community Advisor and Adobe Champion
          August 28, 2018

          Perfect.  That's the answer I was looking for.  Thanks!

            Terms & ConditionsAccessibility statement

            Loading footer...