Hi,

We're evaluating PushWoosh and managed to get it going pretty quickly, 20 mins from start to finish which was nice.

One of the areas we are looking at is how PushWoosh handles device segmentation. Our servers can send out updates to user apps every few minutes, though it can often go hours and not send anything out to somebody.

The users we update are very dynamic, one minute we could have 2,000 users needing an update, five minutes later we could have a different 1,500 users needing an update, five minutes later it could be some combination of the first two updates and five minutes later it could be completely different again.

We actually have no difficulties doing this device segmentation ourselves, we've written all the code for this and we're comfortable it works quickly and well.

The PushWoosh documentation also talks about segmentation (http://docs.pushwoosh.com/docs/segmentation-tags-and-filters) and we want to make sure that our approach for device segmentation is acceptable. We are happy writing to the REST API and making sure that we don't have more than 1,000 devices in each of our REST API calls, but were nervous that this might not be the right way to do things.

Any advice or guidance welcomed.

Thanks,

Rob

asked 21 Dec '15, 17:58
rwillett's gravatar image

rwillett
2015

We do something like this. Over 40,000 devices and we store the device IDs in our own database. When we need to push we look up the user's device ID and push to that single device. But our users could have multiple devices, so we actually gather all those device HWIDs into an array and push to all of them. This doesn't seem different from your scenario EXCEPT that we don't push to a 2,000 person segment. The issue I see there would be memory constraints on passing all that data to the PushWoosh API calls. I think you'd have to loop through them, gathering up as many as you can in each loop until you run into memory limits for the array of HWIDs that you'll send in each loop.

permanent link
answered 23 hours ago
Earl's gravatar image

Earl
13

edited 23 hours ago

Thanks for this.

Our situation is very few messages may need to go very many users. So as you suggest we split the list down so that we don't hit the PushWoosh API limits. Pretty simple coding.

Rob

permanent link
answered 23 hours ago
rwillett's gravatar image

rwillett
2015

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×181
×104
×61

question asked: 21 Dec '15, 17:58

question was seen: 2,541 times

last updated: 23 hours ago