<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/feed.rss.xml" type="text/xsl" media="screen"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>gridN/A</title>
    <description/>
    <link>https://speakerdeck.com/gridna</link>
    <atom:link rel="self" type="application/rss+xml" href="https://speakerdeck.com/gridna.rss"/>
    <lastBuildDate>2017-09-22 05:07:38 -0400</lastBuildDate>
    <item>
      <title>TRACKING CONCEPT IN ZALANDO APP</title>
      <description>Tracking is very important part of any application - it helps to discover weak and strong features, track revenue, analyse user behaviour. This information is necessary to improve app user experience, have better picture of company goals and provide direction for the app strategy. The Zalando App team has implemented a tracking system and keep improving it. In my talk I would like to share our solutions and a main concept on how do we "cook" tracking in Zalando App.</description>
      <media:content url="https://files.speakerdeck.com/presentations/2c3ed005b12243c9ad6b7077cd33f82f/preview_slide_0.jpg?8610747" type="image/jpeg" medium="image"/>
      <content:encoded>Tracking is very important part of any application - it helps to discover weak and strong features, track revenue, analyse user behaviour. This information is necessary to improve app user experience, have better picture of company goals and provide direction for the app strategy. The Zalando App team has implemented a tracking system and keep improving it. In my talk I would like to share our solutions and a main concept on how do we "cook" tracking in Zalando App.</content:encoded>
      <pubDate>Fri, 22 Sep 2017 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/gridna/tracking-concept-in-zalando-app</link>
      <guid>https://speakerdeck.com/gridna/tracking-concept-in-zalando-app</guid>
    </item>
  </channel>
</rss>
