Hi Dinusha,
Earlier we are sending the one tracking ID and we validated that against
the context to ensure that user is sending the tracking ID which is
generated by App manager.

But when we create multiple proxy apps for a real web app, we should allow
to send multiple tracking IDs in the request. It can be done via sending an
array of tracking IDs in the request.

Thanks,
Rajeeva.


On Fri, May 2, 2014 at 1:10 PM, Dinusha Senanayaka <[email protected]> wrote:

>
>
>
> On Thu, May 1, 2014 at 5:14 PM, Rajeeva Uthayasangar <[email protected]>wrote:
>
>> Hi Dinusha,
>> In BAM scenario, tracking ID is generated based on context and version of
>> the proxy web app in app manager.So if we create two proxy web apps for a
>> real app, tracing ID will be unique.
>>
>> And in the Handler, we are validating the tracking ID against the context
>> before publish.
>>
>
> Scenario that i'm telling is something like this,
>
> Actual web-app    Gatewaycontext    Trackingcode
>
> Web-App-A             (i) /myapp1             (i) trackingCode1
>
>                                 (ii) /myapp2            (ii) trackingCode2
>
>
> If we include trackingCode1 into web-app-A then only the /myapp1 requests
> will be counts for the stats according to this "we are validating the
> tracking ID against the context before publish". If user needs the stats
> for both (i) & (ii), then we should be able to include both tracking codes
> into web-app-A.
>
>
> Anyway, we ll talk FF about this on Monday.
>
>
> Regards,
>
> Dinusha.
>
>
>
>>
>> Thanks,
>> Rajeeva
>>
>>
>> On Thu, May 1, 2014 at 1:55 PM, Ravi Undupitiya <[email protected]> wrote:
>>
>>> Hi Dinusha,
>>>
>>> From the GA perspective, I don't think this is an issue (if I'm
>>> understanding you correctly, sorry if i'm not).
>>>
>>> Currently the unique ID sent to google analytics is stored in a cookie
>>> that takes the API name into consideration. So for each app manager app in
>>> your scenario (even if they use the same backend app) there will be two
>>> unique ID's - and hence will be treated as separate invocations (also the
>>> document paths stored will be different - it will be up to the user to
>>> identify the different apps on GA by looking at the paths) .
>>>
>>> For both applications, if we use the same tracking code, it doesn't
>>> matter as we create two unique ID's as explained above.
>>>
>>>
>>> On Thu, May 1, 2014 at 12:06 PM, Dinusha Senanayaka <[email protected]>wrote:
>>>
>>>>
>>>> Hi,
>>>>
>>>> $subject is something practical (AFAIS).
>>>>
>>>> Say we have a web-app "A". Then we have published two applications in
>>>> AppM by pointing to the web-app "A" as endpoint. If we need to collect
>>>> stats, we need to include the tracking code generated by AppM for that
>>>> particular web-app.
>>>>
>>>> Can we include multiple tracking codes with the js script that we are
>>>> using ? (If we include only single code,then the counters will not be
>>>> correct)
>>>>
>>>> Regards,
>>>> Dinusha.
>>>>
>>>> --
>>>> Dinusha Dilrukshi
>>>> Senior Software Engineer
>>>> WSO2 Inc.: http://wso2.com/
>>>> Mobile: +94725255071
>>>> Blog: http://dinushasblog.blogspot.com/
>>>>
>>>
>>>
>>>
>>> --
>>> *Ravi Undupitiya*
>>> Software Engineer; WSO2 Inc.; http://wso2.com
>>>
>>>
>>> *E-mail: [email protected] <http://wso2.com>**M: **+94 772 930 712
>>> <%2B94%C2%A0772%20930%20712>*
>>>
>>> Lean . Enterprise . Middleware
>>>
>>
>>
>>
>> --
>> *Rajeeva Uthayasangar*
>> Software Engineer
>> WSO2, Inc.:http://wso2.com
>>
>>
>> Mobile: +94777298873
>>
>>
>
>
> --
> Dinusha Dilrukshi
> Senior Software Engineer
> WSO2 Inc.: http://wso2.com/
> Mobile: +94725255071
> Blog: http://dinushasblog.blogspot.com/
>



-- 
*Rajeeva Uthayasangar*
Software Engineer
WSO2, Inc.:http://wso2.com


Mobile: +94777298873
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to