Renditions versus analytics - identifying folios

If we're using renditions to serve hi-/low- res content to different iPads, I believe the folio names need to be the same for the different versions. I think this means that in analytics we won't be able to differentiate individual folio downloads for the different resolutions folios, is that right?
Thanks,
Toby

If you have Site Catalyst you can break the folio downloads down by device name, or use a segment to only look at downloads for a specific set of devices. Then you can get numbers for the different resolution folios.
Neil

Similar Messages

  • Quick way to upload renditions of the same folio?

    Hi again,
    I'm  presently uploading on the folio producer 3 renditions of the same folio. My question is: is there a way to upload once the "heavy" things (video for example) and then only upload the various layout or is it necessary to upload all the links for each rendition (and this is very, very longtime!)?

    I don't think you can send the same ports to two different LAN IP addresses.  Also, I don't think you really want to do this.
    The router is like a mailman.  In order to get the mail (incoming data) to the correct home (computer), each home (computer) must have a unique address.   Likewise, a letter (incoming data) can be delivered to only one home (computer).
    If incoming data on port 3074, intended for your computer, said that you get 10 points added to your game score, would you really want your friend to get 10 points also ?  If the same data was sent to 2  xboxes, that's exactly what would happen.
    Internet games are usually setup so that different ports are used for different players.  For example, you might use port 3074, and your friend would use port 3075.   I assume that the xbox can do this.  If not, then you probably cannot play two xboxes on a single Internet connection.

  • Is there a way to track analytics on folios viewed through Content Viewer?

    We'd like to gain some insight into how our testers use the app

    As suggested above, you may use Google Analytics, for which you would need to include their Javascript in your Folio. The problem with these are that the data recorded may not be accurate since reporting is not reliable when the device is Offline, plus it's additional work to include the script.

  • Reading Analytics Multi Folio

    Hello,
    I am able view the individual folio count, but i would like to view the download count of the app itself. Am I able to do that?

    If you are looking to get a count of # of times your app is downloaded, we recommend that you get this number directly from the appstores.
    If you are in DPS base analytics dashboard on digitalpublishing.acrobat.com, then "App First Time Launches" report will give you a trend on first time launches for an app (i.e. app installed and launched for the first time).

  • How to identify Folio Builder Panel version?

    I'm very grateful that Adobe finally start to put info about version of each component to name of download archive, it's less mess now.
    But i'm still lost when i need to identify which version of Folio Builder Panel is installed on each computer. How to the hell i can find out from this if i have 1.9 or 1.9.1?
    12.1.3.20120307_m_680879 - this is NOT user friendly
    Thanks for help!
    M.

    The version number 1.9.1 refers to the producer tools. You find it in the
    info panel of the folio builder panel.
    Sadly (very sadly) it still says 1.9 even when you have 1.9.1 installed.
    The long version number you see in light grey (and the info window) shows
    the panel version and it's release date. In your case 7th march, 2012.
    I have detailed info about version numbers at caniupdateadobedps.com
    —Johannes
    (mobil gesendet)

  • Multi rendition folio size

    hi there,
    i've read an article about Apple forcing us to build (at least) retina versions of our new apps, starting from Mai 2013.
    Can someone tell me if this really true ?
    If I want to build multi-renditions or retina versions:
    - is it right to work with photoshop (layered PSD) images at 264dpi and scale them down as needed inside InDesign or is it better to do all scaling inside Photoshop and do a 'safe for web' as JPG ?
    - do I have to include video at 1080p or will 720p be enough ?
    At this point I did a little test. Adobe Media Encoder created 720p and 1080p versions of each videoclip in a magazine. Inside the InDesign document I've linked to the 720p videofile. Filesize of the folio on the iPad was 478Mb.
    Then I've put the 1080p versions inside a 'HD' folder together with the corresponding 720p file. Filesize of the folio grows to 932Mb.
    Can someone inform me if this the way we have to build our folio's from Mai 2013 on ?
    Thanks in advance,
    Herman Belgy

    Hi there. I have been uploading my articles as a PDF as we discussed, so that every ipad version can have the highest res possible.
    Bob, you said I should ignore this link...
    http://helpx.adobe.com/digital-publishing-suite/help/creating-dps-content-different-ipad.h tml
    I'm still confused.
    Should I be doing this? (as stated in link) (My articles are horizontal only and 1024x768)
    Create 1024x768 and 2048x1536 renditions
    When you create folio renditions, the iPad SD models display only the 1024x768 rendition and the iPad HD displays only the 2048x1536 rendition. You can use either the same set of source files (recommended) or two different sets of source files to create the renditions. For additional guidance, see the articles by Bob Bringhurst and Colin Fleming linked below.

  • How do I publish multiple renditions??

    I am trying to get my first app on the app store, and I want an SD version and an HD version. I've been reading all of these discussions and I am confused... I am using single edition, so di I only need one serial number, or two? If only one, should my file be one InDesign file with 2 renditions, or should I create two different files, one for SD and one for HD? I tried both ways, but when I downloaded the test file for the single InDesign file with 2 renditions, only the SD version shows up on my HD iPad. When I try two InDesign files, I started with the HD version, got all the way to the point where I can download and test an HD version, but then when I try to create an SD version I am not allowed because the serial number is already used by the HD version. HELP! How does this work???? I can't find any documentation online that is a step by step process for this. Also, my files will not upload as PDF, they fail every time so I am uploading as Automatic.

    If you're creating a Single Edition app, you cannot use folio renditions because only one folio can be included in a Single Edition app. Instead, use a feature called "multi-rendition articles," which is a way of creating articles that look good on both HD and SD devices. See this article:
    http://help.adobe.com/en_US/digitalpubsuite/using/WS804da476e1fb25e6276784b6139c71bed03-80 00.html

  • How does the choice of folio name affect publishing

    Getting ready to publish for the first time and wondering how the folio name or the publication name affects anything going to apple. I am guessing the publication name and folio number live on in the app navigation, but not sure about the folio name. Also, it seems the screen names for the app is limited to 12 characters or so on the iPad--I am assuming you name the app when you go to the app store to publish?
    Thanks in advance.

    The Folio Name is used internally -- it appears in the panel, but not in the viewer. The Folio Name is useful for tasks such as setting up folio renditions and linking across folios. The Publication Name and Folio Number appear in the viewer app library and in browsing structures such as the table of contents and browse mode. If you look in the library of The New Yorker app, they use "The New Yorker" for the Publication Name and "October 13, 2012" for the Folio Number. (In my DPS Tips app, I reverse it by using the folio name for Publication Name and the app name for Folio Number for aesthetic reasons. You can use these settings however you want.)
    You specify the app name when you build the app in Viewer Builder. You can use about 13 characters, more if the characters are skinny ("Illial") and fewer if the characters are wide ("WOWZOW").

  • Updating rendition with new size

    Hi there,
    Here's the situation, its a little tricky to word, but I'll do my best.
    I've published an iPad-sized folio to Android (1024*768/768*1024.) It shows up in the Viewer app letterboxed. Works fine.
    I've now completed a new folio, that is sized for Android (Xoom.)
    I'd like to replace the old (iPad-sized) folio, with the new one.
    So my question;
    Do I "Remove" the old and then "Publish" the new?
    or is there a way that I can "Update" the old (iPad-sized) with the new (Android-sized) folio?
    Thanks for any help,
    DW

    Yes, you'll want to remove (unpublish) the older 1024x768 folio and then publish the new Android-sized folio. If you're creating renditions, make sure the Folio Name and Product ID values are identical to the iPad version. In fact, it's best to use the same folio metadata (Folio Name, Publication Name, Folio Number) for renditions.See Create folio renditions for more information.

  • Folio not appearing in Adobe Content Viewer on some iPads

    I have been working on developing an app for iPad in InDesign CS6 using Adobe DPS. For the most part, the process was working smoothly until recently. Once signed into Adobe Content Viewer on my third generation iPad, the folio shows up fine and downloads as expected. However, when others with older iPads download Content Viewer and sign in, they do not see the folio as an option. For example, a person with a second generation iPad, who has the latest iOS, was unable to see the folio in the viewer. I have stripped the app down to about 40megs, thinking size might have been an issue, but after multiple users have experience identical results, I don't think that is it. Has anyone had a similar issue, and is there anything I can do on my end to make the app compatible with a wider range of iPads?

    Is it a single-folio app or a multi-folio app? If you set up renditions for a multi-folio app, only the appropriate rendition is available for a device. See this article about renditions:
    http://help.adobe.com/en_US/digitalpubsuite/using/WS9293e1fb3b977c5c-2337961812e35738f56-8 000.html

  • Handling legacy PDF-format folios in Kindle viewer

    I'm working with a client to publish a magazine on the Kindle Fire. The magazine, a bimonthly, has been available on the iPad for more than a year now. All of the folios that we have produced for the iPad are PDF format. (Which turned out to be a good decision, since they will display nicely on the new iPad.)
    We will produce a 1024x600 rendition for the Kindle going forward. However, all of the legacy folios show up in the Kindle viewer library and are not readable. The reader displays an error when you try to open one of the old folios. ("This folio contains one or more PDF stacks which are not yet supported ...")
    I would like to prevent some frustration for our readers here, but we do not have the budget or time to rebuild all of the legacy folios as 1024x600 documents.
    The Kindle will adequately display 1024x768 PNG-based folios by adding bars at the top and bottom of the screen. Not ideal, but adequate. If we were to shave a few pixels -- say, 4 or 6 -- from the width of the legacy folios and rebuild them as PNG-based folios, would the difference be enough for the Kindle to recognize those as renditions and load them instead of the full-size folios? And would the iPad ignore the slightly narrower folios? That would allow us to address the problem without having to redesign a years' worth of magazines.
    Thanks to Adobe and Amazon for working out the issues with the Kindle viewer. Looking foward to seeing our publications on both platforms soon.
    SB

    If you set up renditions (same Folio Name, different Size values) between folios, it should work. Try shaving off one pixel and creating a 1024x767 folio and source documents. It definitely won't show up on the iPad (iPads viewers display 4:3 aspect ratio folios only), and if you set up renditions properly, the 1024x768 folio won't show up on Android.

  • Adobe Content Viewer v22 for Android - folio update issue

    Yesterday I updated our Xoom to Android 4.1.1 and updated the Adobe Content Viewer to v22.  Both we and a client have had issues with not seeing the "Update Available" message for folios that are been updated.  The "Updating Library..." message flashes briefly at the top of the viewer in library mode, however nothing changes.  It's only after killing the app and restarting that it takes its time while checking the library for updates and finds them.  Has anyone else had this issue?  The iPad rendition of the same folio has been showing update messages in the usual, almost instantaneous, way.
    Has anyone else had difficulty with updating folios in the Android v22 Adobe Content Viewer?  In the past couple of versions I've noticed some strangeness with the Sign In/ Sign Out part of the library where it seems like the text tells you you're signed in, but sometimes you have to sign out and sign back in to get updates.  Sometimes you could go back to the home screen and then go back into the app and it would trigger a check for updates as well, however that trick doesn't seem to be working anymore.
    Andrew

    Thank you for the reply Himanshu.  Evidently the problem is much worse than I thought because previously created apps don't even open anymore!
    None of the apps we have published to the Android app store are getting past the splash screen.  The library flashes briefly on some of them before the app crashes.  The error message it gives is "Unfortunately, ____ has stopped."  This is a big problem!!  Will updating the apps to v22 solve this issue?  When will Adobe have this major problem fixed?
    I'm flashing back to June of last year when reliability of basic functionality (like apps opening and folios being downloadable/viewable) was still unpredictable.  You Adobe guys and gals have got to figure out how to make the DPS system dependable.  I understand this is an operating system conflict, but surely you knew this update was coming and could test how well your software would hold up to the changes.  This isn't a barely used minor feature that isn't working, this is something that makes users uninstall the app and lessens their opinion of the company that released it.  Please make this your top priority and get it fixed today.  We and our customers are paying for a much higher level of service than this.

  • Rebuilding Android Folios

    Hello, I'm looking for suggestions on workflow for Android 7" tablets. We currently have apps in both iTunes an GooglePlay store (and Amazon). Until now, I had been using the 1024x768 to build folios across all devices. However, we just bought a Google Nexus 7 and downloaded our app only to discover that our folios are unreadable due to the ratio being 4:3 and not 3:2. I would like to rebuild our folios for the Android tablet but since they are already published I'm not certain where to begin.
    If i take the "Lazy Susan" approach per Bob's scenario #1 (referencing article "Creating DPS Folios for Android Devices") and reuse my iPad documents and make a 1600x1200 size, would I need to:
    1) unpublish and then republish the folio?
    2) Is it okay to reuse the the same publication ID?
    3) If so, what happens to the Amazon version?
    4) Does it matter if I decide to only make a "V" orientation document when it was previously both?
    5) Will the user then have to download the "new" folio and delete/archive the previously published folio?
    I assume if I choose to either go "Whole Hog" and/or "Sensible Shortcuts", both of these processes would have the same above questions (unpublish/republish, etc.) I'm thinking it's okay to add renditions at this point since it is "sort of" a "new" folio...Is that correct?
    Any help would be appreciated. Thank you.

    If you looked at your app on a larger HD Android tablet, you'd be even more disappointed in how your 1024x768 folio looks. It looks like a small stamp in the middle of a black screen. That's the big drawback to the "Lazy Susan" approach, at least for now. (In an upcoming release, Android viewers should be able to scale content up or down. That will simplify matters, and I'll need to revise my guidance.)
    1) There is no reason to unpublish/republish the folio. Just create a new 1600x1200 rendition using the same Folio Name, Product ID, and Publication Date settings used in the 1024x768 folio. Of course, the problem to this approach is that 1600x1200 is still 4:3 aspect ratio, which doesn't look great on 16:9-ish devices. Consider creating 1280x800 source files for the Android and repurposing those for each rendition.
    2) What do you mean by reusing the same "publication ID"? If you mean using the same Application role/Title ID for iOS and Android, yes you can, but it frequently complicates matters. It's usually easier to create separate accounts (Title IDs) for iOS and Android. If you mean something else by "publication ID," please clarify.
    3) The Amazon version should be fine, unless you turned on Strict Renditions (which you don't want to do in your case). Again, I may not understand the question.
    4) It's no problem to create a dual-orientation folio for one rendition and a single-orientation folio for another rendition.
    5) That's a little tricky. If a user has already opened the app, the viewer registers the 1024x768 rendition and unfortunately doesn't check for a new rendition until the app itself in uninstalled/reinstalled.
    Regarding your question about adding renditions at this point, that's perfectly fine. Adding renditions doesn't hurt existing users, and it makes things better for your new users.
    The key to success is to make sure that you set up your source files so that they can be imported easily. Most publishers take the "Sensible Shortcuts" route and create different renditions based on two or three sets of source files.

  • DPS Analytics

    Do folios published as private show up in the Omniture analytics?

    Folios published as private only appear in Adobe Content Viewer. No analytics get tracked in the Adobe Content Viewer, hence Omniture analytics does not track private folios.
    Shikha

  • DPS analytics access for client only

    Hello
    My internal clients want to access the DPS analytics, but the thing is I am not confortable to give this password and access to several people and also, afraid some would access the Folio Producer and delete or unpublish/publish some content (change the name of my folio etc). Well you had understood me I don't want them to access to the Folio Producer
    Is ther anyway to create an access to just the analytics or create a parallele account??

    No. The account ID assigned an Application role can view Analytics and Folio Producer but not DPS App Builder.

Maybe you are looking for

  • Itunes 7.02

    I have just had a large whiskey, Itunes 7.02 actually syncs with my Ipod Mini - I am ecstatic, it's only taken about a month for Apple to sort it out. My hair is already reverting back to a dark colour from grey. Amazing how such a little annoyance c

  • Starting Desktop impossible in Virtual Box: Unable to delete desktop

    Hi @all, another recurring problem is that some desktop won't start. Trying to do so neither implicitly via regular login nor explicitly via VDI-Manager works. Error throuwn by the Job says: The desktop VDI3-VBox-Adm01 could not be deleted from host

  • Portal session timeout judge

    Hi everybody, I have a question about portal session timeout. Now we have a javascript for session timeout in Masthead iview, which can increase the time for the active user. It uses EPCM to rase the event. But our page has four iveiws, and there is

  • ODI issue during execution

    Hi All I am facing one issue while Loading MEtadata into Hyperion Planning through ODI.I am having around 45k members in Accocount dimension. whenever i am executing interfaces it got completed in 1 second without updating the members,but if i add 1

  • Run script AFTER boot

    I want to run a non-ending script after boot. And I still want to be able to login. So adding the script to rc.local won't fix my problem since the boot process won't finish so that I can login. Adding the script to "dillons" cron doesn't seem to wor